Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 Jul 2007 21:52:15 +0700
From:      Victor Sudakov <vas@mpeks.tomsk.su>
To:        freebsd-questions@freebsd.org
Subject:   Re: dump -L
Message-ID:  <20070724145215.GA3087@admin.sibptus.tomsk.ru>
In-Reply-To: <20070724134431.GA57022@epia-2.farid-hajji.net>
References:  <20070724115401.GA1355@admin.sibptus.tomsk.ru> <20070724134431.GA57022@epia-2.farid-hajji.net>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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.

> 
> > 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.

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:sudakov@sibptus.tomsk.ru



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20070724145215.GA3087>