From owner-freebsd-questions@FreeBSD.ORG Mon Feb 22 16:38:02 2010 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 D74A1106566B for ; Mon, 22 Feb 2010 16:38:02 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from relay.pcl-ipout01.plus.net (relay.pcl-ipout01.plus.net [212.159.7.99]) by mx1.freebsd.org (Postfix) with ESMTP id 6F4E38FC17 for ; Mon, 22 Feb 2010 16:38:02 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAEhBgktUXebq/2dsb2JhbACbA3O8VYRrBA Received: from relay07.plus.net ([84.93.230.234]) by relay.pcl-ipout01.plus.net with ESMTP; 22 Feb 2010 16:38:00 +0000 Received: from [84.92.153.232] (helo=curlew.milibyte.co.uk) by relay07.plus.net with esmtp (Exim) id 1NjbIG-0006iH-Ig; Mon, 22 Feb 2010 16:38:00 +0000 Received: by curlew.milibyte.co.uk with local (Exim 4.71) (envelope-from ) id 1NjbIG-0000qQ-9W; Mon, 22 Feb 2010 16:38:00 +0000 From: Mike Clarke To: freebsd-questions@freebsd.org Date: Mon, 22 Feb 2010 16:37:59 +0000 User-Agent: KMail/1.9.10 References: <4B828B28.9020703@comclark.com> <20100222150143.GE43687@gizmo.acns.msu.edu> In-Reply-To: <20100222150143.GE43687@gizmo.acns.msu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201002221638.00165.jmc-freebsd2@milibyte.co.uk> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-SA-Exim-Scanned: No (on curlew.milibyte.co.uk); SAEximRunCond expanded to false X-Plusnet-Relay: 0530ef6abf16d39865f07ce672a58315 Cc: Jerry McAllister , Aiza Subject: Re: dump warning msgs?? 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, 22 Feb 2010 16:38:02 -0000 On Monday 22 February 2010, Jerry McAllister wrote: > I don't know the exact algorithm dump uses for sorting the inodes, > but this looks like a file was deleted between the time the list > was made and the time dump got to reading it. I expect it's the inode for the temporary snapshot in the .snap directory. According to the man page this snapshot is unlinked as soon as the dump starts. I assume this is immediately after creating the list of inodes to be backed up, in which case it's in the list but no longer available when the data is dumped. I see the "expected xxx, got yyy" type of message every time I do a restore from a snapshot dump but it's never caused any problems. I've just done a test dump with the -L option and monitored the contents of the partition's .snap directory, a file named dump_snapshot with inode number 4 appeared as I started the dump and then disappeared. I then tried to restore the entire dump to a temporary destination and got a message "expected next file 1319089, got 4". As I expected, the .snapshot directory in the dump was empty with no sign of the dump_snapshot file so I'm assuming that restore put out the warning message when it's list of inodes suggested that number 4 should be the next one but the next sequential file in the dump corresponded to inode 1319089. The wording of the message does however suggest that it actually found the file for inode 4 in the dump when the list of inode numbers indicated that the next sequential file should have been 1319089. I was anticipating the message to be "expected next file 4, got 1319089" -- Mike Clarke