Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 6 Aug 2007 10:57:26 -0400
From:      Jerry McAllister <>
To:        Victor Sudakov <>
Cc:        User Questions <>
Subject:   Re: dump -L
Message-ID:  <>
In-Reply-To: <>
References:  <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Mon, Aug 06, 2007 at 09:56:15AM +0700, Victor Sudakov wrote:

> Victor Sudakov 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 thought this should _never_ happen when dumping a snapshot.
> > 
> > What is it?
> Does nobody know the answer, or am I the only one experiencing the
> problem?
> Here is another example:
> [root@big ~] restore -b64 -rN 
> ./spool/samba.lock/wins.dat: (inode 2829098) not found on tape
> expected next file 267, got 4
> expected next file 2828988, got 2828987

Using 'dump -L' doesn't prevent you or something running on the system
from deleting a file after the directory has been created and written.

The first thing dump does is create a list of files (including directories)
to dump.   It creates a list of inodes for the files and then does all
the dumping from that list of inodes.   If a file is then deleted after
that inode list is made, then it will not get written to the dump media.
But, the list will still have the inode for the file.   When restore
looks for files, it searches in inode order and makes a note if an
inode is missing from the media that it expected (because of the list) to 
be there.    It is only a true error if that file really should have been
there and wasn't.   The only time I have had that happen was when the
media (tape) couldn't be read properly.   Usually then you also get
other errors.


> -- 
> Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
> _______________________________________________
> mailing list
> To unsubscribe, send any mail to ""

Want to link to this message? Use this URL: <>