dump -L

Victor Sudakov sudakov at sibptus.tomsk.ru
Mon Aug 6 00:19:01 PDT 2007


illoai at gmail.com 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?
> 
> I don't know the answer, but I get essentially the
> same behaviour.  I have never seen any data loss,

I gave an example below. The file "wins.dat" was not dumped. It is
indeed missing from the tape.

If this is not a data loss, what is it then?

[root at 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


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


More information about the freebsd-questions mailing list