From owner-freebsd-questions@FreeBSD.ORG Tue Jan 29 15:36:44 2008 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 A80DC16A46E for ; Tue, 29 Jan 2008 15:36:44 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from snoogles.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 5D6D813C4CE for ; Tue, 29 Jan 2008 15:36:44 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (localhost [127.0.0.1]) by snoogles.rachie.is-a-geek.net (Postfix) with ESMTP id 77B1C1CC8B for ; Tue, 29 Jan 2008 06:36:43 -0900 (AKST) From: Mel To: freebsd-questions@freebsd.org Date: Tue, 29 Jan 2008 16:36:41 +0100 User-Agent: KMail/1.9.7 References: <77647f500801281525n534573d6ub3b1794eb947ffbd@mail.gmail.com> <200801291529.50360.fbsd.questions@rachie.is-a-geek.net> <479F3D2D.4060809@dial.pipex.com> In-Reply-To: <479F3D2D.4060809@dial.pipex.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801291636.42156.fbsd.questions@rachie.is-a-geek.net> Subject: Re: restore(1) dumpfile to directory rather than filesystem -- possible? -- SOLVED 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, 29 Jan 2008 15:36:44 -0000 On Tuesday 29 January 2008 15:50:21 Alex Zbyslaw wrote: > Mel wrote: > >man restore: > >-r Restore (rebuild a file system). > > > >This will recreate the filesystem, meaning, the files extracted will have > >identical inode numbers as on the original filesystem. Thus, you will very > >likely run into problems when using this mode. > > > >You're looking for -x, which extracts a dump file, similar to a tar, > > restoring ownership, file times and so on, but leaving the inode numbers > > up to the OS. > > > >restore -x is essentially what OP did interactively. > > Err, no. Not unless it changed recently and this text is still > apparently present in 8-CURRENT (according to the Web interface). > > From the man page BUGS section (though it's been there so long it's a > feature, in my book and belongs better with the -r option to prevent > exactly the confusion you've experienced). Ever tried -r in a directory on a non-new filesystem? I don't recall the exact error, but it can clash. Done restore -x for testing ever since. > A level zero dump must be done after a full restore. Because restore > runs in user code, it has no control over inode allocation; thus a > full dump must be done to get a new set of directories reflecting the new > inode numbering, even though the contents of the files is unchanged. Ah, maybe it's the directories that contain the inode numbers of the old filesystem. Whatever the cause - restore -r *should* only be used on a newfs(8)'d filesystem. -- Mel