From owner-freebsd-questions@FreeBSD.ORG Mon Aug 6 15:51:48 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 6226916A419 for ; Mon, 6 Aug 2007 15:51:48 +0000 (UTC) (envelope-from sudakov@sibptus.tomsk.ru) Received: from relay2.tomsk.ru (relay2.tomsk.ru [212.73.124.8]) by mx1.freebsd.org (Postfix) with ESMTP id A6E5013C48D for ; Mon, 6 Aug 2007 15:51:47 +0000 (UTC) (envelope-from sudakov@sibptus.tomsk.ru) 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 8370864 for freebsd-questions@freebsd.org; Mon, 06 Aug 2007 22:51:43 +0700 Received: (from sudakov@localhost) by admin.sibptus.tomsk.ru (8.13.6/8.13.6/Submit) id l76FphXg027958 for freebsd-questions@freebsd.org; Mon, 6 Aug 2007 22:51:43 +0700 (OMSST) (envelope-from sudakov@sibptus.tomsk.ru) X-Authentication-Warning: admin.sibptus.tomsk.ru: sudakov set sender to sudakov@sibptus.tomsk.ru using -f Date: Mon, 6 Aug 2007 22:51:42 +0700 From: Victor Sudakov To: freebsd-questions@freebsd.org Message-ID: <20070806155142.GB27829@admin.sibptus.tomsk.ru> References: <20070724115401.GA1355@admin.sibptus.tomsk.ru> <20070806025614.GA21368@admin.sibptus.tomsk.ru> <20070806145726.GA64755@gizmo.acns.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070806145726.GA64755@gizmo.acns.msu.edu> 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: Mon, 06 Aug 2007 15:51:48 -0000 Jerry McAllister 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? > > > > Here is another example: > > > > [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 > > Using 'dump -L' doesn't prevent you or something running on the system > from deleting a file after the directory has been created and written. Excuse me? 'dump -L' creates a snapshot which is (or should be) a frozen copy of the filesystem, and then dumps the snapshot. > > The first thing dump does is create a list of files (including directories) > to dump. It creates a list of inodes for the files and then does all > the dumping from that list of inodes. If a file is then deleted after > that inode list is made, then it will not get written to the dump media. How can a file be deleted from a snapshot? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru