Koozali.org: home of the SME Server

buffer (writer): write of data failed: No space left on devi

edward chow

buffer (writer): write of data failed: No space left on devi
« on: April 15, 2003, 02:16:38 PM »
We setup the new e-smith 5.6 server
and use the Hp surestore  DAT40
, DDS-4 20/40GB tape
to backup the system.

Server storage:
----------------------------------------------------------------------------------
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda3              33G   25G  6.9G  78% /
/dev/sda1              99M  8.7M   84M  10% /boot
none                  125M     0  124M   0% /dev/shm

I check the backup log and see the message:
buffer (writer): write of data failed: No space left on device

What problem occur?

Is the hardware fail?
Tape drive not enough buffer?
Backup tape full ?

Please help.
Edward Chow
dsledward@yahoo.com.hk
---------------------------------------------------------------------------
flexbackup version 0.9.8
/etc/flexbackup.conf syntax OK

|------------------------------------------------
| Doing level 0 backup of all using dump
| Retensioning tape...
| Rewinding & erasing tape...
| Creating index key 200304110400.19
| Tape #0
| Filesystems = / /boot
|------------------------------------------------
At block 1.
|------------------------------------------------
| File number 1, index key 200304110400.19
| Backup of: /
| Date of this level 0 backup: Fri Apr 11 04:00:19 2003
| Date of last level 0 backup: the epoch
|------------------------------------------------
| (dump -0 -b 10 -a -f - / | gzip -4) | buffer -m 3m -s 10k -u 100 -t -p 75 -B \
|  -o /dev/nst0
|------------------------------------------------
  DUMP: Date of this level 0 dump: Fri Apr 11 04:00:19 2003
  DUMP: Dumping /dev/sda3 (/) to standard output
  DUMP: Added inode 8 to exclude list (journal inode)
  DUMP: Added inode 7 to exclude list (resize inode)
  DUMP: Label: /
  DUMP: mapping (Pass I) [regular files]
  DUMP: mapping (Pass II) [directories]
  DUMP: estimated 25274667 tape blocks.
  DUMP: Volume 1 started with block 1 at: Fri Apr 11 04:00:58 2003
  DUMP: dumping (Pass III) [directories]
  DUMP: dumping (Pass IV) [regular files]
  DUMP: 0.59% done at 493 kB/s, finished in 14:08
  DUMP: 1.54% done at 648 kB/s, finished in 10:39
  DUMP: 2.33% done at 654 kB/s, finished in 10:28
  DUMP: 3.02% done at 636 kB/s, finished in 10:41
                                 .
                                 .
                                 .
  DUMP: 95.00% done at 734 kB/s, finished in 0:28
  DUMP: 95.77% done at 733 kB/s, finished in 0:24
  DUMP: 97.10% done at 736 kB/s, finished in 0:16
buffer (writer): write of data failed: No space left on device
bytes to write=10240, bytes written=-1, total written   16657260K
  DUMP: Broken pipe
  DUMP: The ENTIRE dump is aborted.

Pierluigi Miranda

Re: buffer (writer): write of data failed: No space left on
« Reply #1 on: April 15, 2003, 03:21:22 PM »
Edward Chow wrote:

> We setup the new e-smith 5.6 server
> and use the Hp surestore  DAT40
> , DDS-4 20/40GB tape
> to backup the system.
>
> Server storage:
> ----------------------------------------------------------------------------------
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/sda3              33G   25G  6.9G  78% /
[...]
> I check the backup log and see the message:
> buffer (writer): write of data failed: No space left on device
>
> What problem occur?

Been there, seen that...

As you guessed, the problem is that the tape is full.

Using backup devices one must keep in mind that their real available capacity is the first figure; the second one is an estimate of what can be stored if the data can be compressed with a 2:1 ratio.

So, you hav to think about your tape unit as a 20 GB one.

If a system contains many already compressed files - zipped or gzipped files, jpeg images i.e. the ones in the squid cache, it can happen that the mean compression ratio is way lower that the estimated 2:1, or worse, lower than 1:1 - the subsequent compression actually increas the size of the already compressed files.

Can your server fall in this cathegory?

By default flexbackup compresses data with gzip before saving them on tape, that in turn compresses the data stream again, so it can happen that the net result is a slightly expanded save set.

If you want an optimized backup operation, you should experiment with flexbackup parameters - block size (32 KB?), compression on/off, data backup utility (tar vs. dump), and maybe a different backup strategy, making more selective backups of different file system subtrees.

Or you can simply keep your disk lean - or buy a larger capacity backup unit :)

--

Pierluigi Miranda

Ray Mitchell

Re: buffer (writer): write of data failed: No space left on
« Reply #2 on: April 16, 2003, 08:26:18 PM »
Or you could try using Arkeia backup instead of flexbackup. There is a sme integrated version which replaces flexbackup or you can use Arkeia via a java applet on your workstation. Both ways you can control (in different ways) what data you want to backup thus keeping your backed up data within the tape drive limits.

Search these forums for Arkeia (all dates) as there is some useful information already posted (particularly the more recent stuff).
Regards
Ray Mitchell