From: Stelian P. <st...@po...> - 2004-06-17 09:04:09
|
On Mon, Jun 14, 2004 at 11:57:46AM -0700, Ken Godee wrote: > >>I'm wondering what happens when it runs out of space, it didn't > >>abort and seemed to finish ok, but did it really? > >>If not, shouldn't of aborted? > > > >It should have. Looking at the code is seems like it should > >have aborted with something like: > > "cannot write to file /tmp/rstdir..." > > > > I'm probally wrong here. It probally did abort, > I forgot the script is in a "for loop" probally > just continued on to next dump. I've created a 300k temp filesystem and used it as the temp directory: # df /mnt/toto/ Filesystem 1K-blocks Used Available Use% Mounted on /tmp/FILE 290 13 262 5% /mnt/toto # restore ifT home.dump.001 /mnt/toto/ restore: cannot write to file /mnt/toto//rstdir1080569410-aVo9aJ: No space left on device So it does seem to work as it should... > >>My real concern would be during an actual restore, I'm > >>sure the same would happen. > > > >Do you use the latest version of restore ? > 0.4b36 > > I'm just looking forward at diaster recovery > and I'll just have to make sure that whatever CD solution > I use will have kernel support for ram disks or make a small partition > available. It's always a good idea to think at those things *before* you really need to restore :) > Redhat's default partition scheme is nutty, one big root partition > and several systems I need to back up have been set up this way. > Very dangerous, well maybe as soon as I get some time I'll add > to the list. Indeed. Stelian. -- Stelian Pop <st...@po...> |