Jerry McAllister 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: > > > > [EMAIL PROTECTED] ~] 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.
Excuse me? 'dump -L' creates a snapshot which is (or should be) a frozen copy of the filesystem, and then dumps the snapshot. > > 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. How can a file be deleted from a snapshot? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:[EMAIL PROTECTED] _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
