Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 6 Aug 2007 01:22:05 -0500
From:      "illoai@gmail.com" <illoai@gmail.com>
To:        "Victor Sudakov" <sudakov@sibptus.tomsk.ru>
Cc:        User Questions <freebsd-questions@freebsd.org>
Subject:   Re: dump -L
Message-ID:  <d7195cff0708052322x256816f8r1b4d5b1a30ac269f@mail.gmail.com>
In-Reply-To: <20070806025614.GA21368@admin.sibptus.tomsk.ru>
References:  <20070724115401.GA1355@admin.sibptus.tomsk.ru> <20070806025614.GA21368@admin.sibptus.tomsk.ru>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 05/08/07, Victor Sudakov <sudakov@sibptus.tomsk.ru> 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?

I don't know the answer, but I get essentially the
same behaviour.  I have never seen any data loss,
though.  I just tended to assume it was either harmless
or the world was going to end, neither of which cases
I could seem to rule out definitively.

-- 
--



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?d7195cff0708052322x256816f8r1b4d5b1a30ac269f>