Date: Wed, 25 Jul 2007 08:56:11 +0700 From: Victor Sudakov <sudakov@sibptus.tomsk.ru> To: freebsd-questions@freebsd.org Subject: Re: dump -L Message-ID: <20070725015611.GA14831@admin.sibptus.tomsk.ru> In-Reply-To: <44d4yh3evo.fsf@be-well.ilk.org> References: <20070724115401.GA1355@admin.sibptus.tomsk.ru> <20070724134431.GA57022@epia-2.farid-hajji.net> <20070724145215.GA3087@admin.sibptus.tomsk.ru> <44d4yh3evo.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Lowell Gilbert wrote: > >> > > >> > I always use "dump -L" to dump a live filesystem. > >> > However, when I restore the dump, I sometimes get messages like > >> > "foo.txt (inode 12345) not found on tape" or > >> > "expected next file 12345, got 23456" > >> > >> I'm seeing this too. It's always exactly one inode per file system. > > > > You are probably talking about "expected next file 12345, got 23456". > > It seems harmless. > > > > But I am more worried about "foo.txt (inode 12345) not found on tape". > > Indeed, some files fail to get into the dump. > > Are the files active at the time of the dump? Yes, they are. These are files edited by Samba users, mrtg files etc. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070725015611.GA14831>