Date: Mon, 6 Aug 2007 14:18:57 +0700 From: Victor Sudakov <sudakov@sibptus.tomsk.ru> To: freebsd-questions@freebsd.org Subject: Re: dump -L Message-ID: <20070806071857.GA23813@admin.sibptus.tomsk.ru> In-Reply-To: <d7195cff0708052322x256816f8r1b4d5b1a30ac269f@mail.gmail.com> References: <20070724115401.GA1355@admin.sibptus.tomsk.ru> <20070806025614.GA21368@admin.sibptus.tomsk.ru> <d7195cff0708052322x256816f8r1b4d5b1a30ac269f@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
illoai@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@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@sibptus.tomsk.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070806071857.GA23813>