From owner-freebsd-questions@FreeBSD.ORG Tue Jul 24 15:52:20 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 1CE9916A418 for ; Tue, 24 Jul 2007 15:52:20 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from relay2.tomsk.ru (relay2.tomsk.ru [212.73.124.8]) by mx1.freebsd.org (Postfix) with ESMTP id 700CF13C469 for ; Tue, 24 Jul 2007 15:52:18 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) X-Virus-Scanned: by Dr.Web (R) daemon for FreeBSD, v4.33 at relay2.tomsk.ru Received: from [172.16.138.125] (account sudakovva@sibptus.tomsk.ru HELO admin.sibptus.tomsk.ru) by relay2.tomsk.ru (CommuniGate Pro SMTP 4.3.8) with ESMTPSA id 8231898 for freebsd-questions@freebsd.org; Tue, 24 Jul 2007 21:52:16 +0700 Received: (from sudakov@localhost) by admin.sibptus.tomsk.ru (8.13.6/8.13.6/Submit) id l6OEqFvT003160 for freebsd-questions@freebsd.org; Tue, 24 Jul 2007 21:52:15 +0700 (OMSST) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.tomsk.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Tue, 24 Jul 2007 21:52:15 +0700 From: Victor Sudakov To: freebsd-questions@freebsd.org Message-ID: <20070724145215.GA3087@admin.sibptus.tomsk.ru> References: <20070724115401.GA1355@admin.sibptus.tomsk.ru> <20070724134431.GA57022@epia-2.farid-hajji.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070724134431.GA57022@epia-2.farid-hajji.net> User-Agent: Mutt/1.4.2.1i Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://vas.tomsk.ru/vas.asc Subject: Re: dump -L X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2007 15:52:20 -0000 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. > > > 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. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru