From owner-freebsd-questions@FreeBSD.ORG Tue Jul 24 17:12:14 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08A7C16A41F for ; Tue, 24 Jul 2007 17:12:14 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail8.sea5.speakeasy.net (mail8.sea5.speakeasy.net [69.17.117.10]) by mx1.freebsd.org (Postfix) with ESMTP id D54CE13C4D9 for ; Tue, 24 Jul 2007 17:12:13 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 22386 invoked from network); 24 Jul 2007 17:12:13 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail8.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 24 Jul 2007 17:12:13 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 1276428440; Tue, 24 Jul 2007 13:12:11 -0400 (EDT) To: Victor Sudakov References: <20070724115401.GA1355@admin.sibptus.tomsk.ru> <20070724134431.GA57022@epia-2.farid-hajji.net> <20070724145215.GA3087@admin.sibptus.tomsk.ru> From: Lowell Gilbert Date: Tue, 24 Jul 2007 13:12:11 -0400 In-Reply-To: <20070724145215.GA3087@admin.sibptus.tomsk.ru> (Victor Sudakov's message of "Tue\, 24 Jul 2007 21\:52\:15 +0700") Message-ID: <44d4yh3evo.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.99 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: dump -L X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2007 17:12:14 -0000 Victor Sudakov 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?