backups on 386/ix - some pronblems using GNUtar; any hints?
pcg at aber-cs.UUCP
Fri Dec 8 03:56:05 AEST 1989
In article <1989Dec5.012032.2877 at virtech.uucp> cpcahil at virtech.uucp (Conor P. Cahill) writes:
In article <481 at hades.OZ>, greyham at hades.OZ (Greyham Stoney) writes:
> 1) When the tape is completely full, GNUtar reports "error opening
> directory ...." for every directory not yet covered. At least, this seems
> to be what's happening. If the tape drive is 120Mb, and the filesystem is
> 115Mb, how come the tape fills up at all anyway when doing a full dump???.
This is probably because you have some sparse files on the file system. When
they get backed up, they take up the logical amount of space, not the physical
amount of space taken up on the file system.
A likely reason would be that GNU tar, while walking the filesystem tree,
forgets to close directories that it has opened, when unstacking them and
thus runs out of file descriptor slots. Since a typical 386 unix has 60 fd
slots per process, this may take a while, and make you believe that you have
dumped too much.
Piercarlo "Peter" Grandi | ARPA: pcg%cs.aber.ac.uk at nsfnet-relay.ac.uk
Dept of CS, UCW Aberystwyth | UUCP: ...!mcvax!ukc!aber-cs!pcg
Penglais, Aberystwyth SY23 3BZ, UK | INET: pcg at cs.aber.ac.uk
More information about the Comp.unix.i386