Victor Sudakov <[EMAIL PROTECTED]> 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? _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
