Date: Tue, 24 Jul 2007 13:12:11 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Victor Sudakov <vas@mpeks.tomsk.su> Cc: freebsd-questions@freebsd.org Subject: Re: dump -L Message-ID: <44d4yh3evo.fsf@be-well.ilk.org> In-Reply-To: <20070724145215.GA3087@admin.sibptus.tomsk.ru> (Victor Sudakov's message of "Tue\, 24 Jul 2007 21\:52\:15 %2B0700") References: <20070724115401.GA1355@admin.sibptus.tomsk.ru> <20070724134431.GA57022@epia-2.farid-hajji.net> <20070724145215.GA3087@admin.sibptus.tomsk.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Victor Sudakov <vas@mpeks.tomsk.su> writes: > cpghost 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? >> >> > I thought this should _never_ happen when dumping a snapshot. >> > >> > What is it? >> >> I don't know. Perhaps it is the inode of the snapshot file >> itself? > > "find -inum" does not support this assumtion. Do you mean that you can't find the file at all in the snapshot?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44d4yh3evo.fsf>