From owner-freebsd-current@FreeBSD.ORG Tue Jul 6 16:55:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1242B16A4CE; Tue, 6 Jul 2004 16:55:57 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0BFA43D2D; Tue, 6 Jul 2004 16:55:56 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id i66Gtt2G012654; Tue, 6 Jul 2004 09:55:55 -0700 (PDT) Received: from [10.1.1.193] (nfw2.codefab.com [199.103.21.225] (may be forged)) (authenticated bits=0)i66Gts04025357; Tue, 6 Jul 2004 09:55:54 -0700 (PDT) In-Reply-To: <200407052151.i65LouOV002134@gw.catspoiler.org> References: <200407052151.i65LouOV002134@gw.catspoiler.org> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <579308A2-CF6D-11D8-911E-003065ABFD92@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Tue, 6 Jul 2004 12:55:53 -0400 To: Don Lewis X-Mailer: Apple Mail (2.618) cc: freebsd-current@FreeBSD.org cc: damaker@fillibach.de Subject: Re: moving /usr to another partition X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2004 16:55:57 -0000 On Jul 5, 2004, at 5:50 PM, Don Lewis wrote: > On 5 Jul, Konstantin 'Kosta' Welke wrote: >> Diskspace is running low, so I'd like to move my /usr to another >> disk. [ ... ] If you have any hints or alternatives, please let me >> know! "rsync -a" is a pretty good way of backing up a tree of stuff. You can also use a tar pipeline as per it's manpage. > I'm pretty sure that "restore -r" will do the right thing and just > unpack the dump archive into the current working directory. I'm pretty > sure that I've done this in the past. > > I don't understand the warnings in the man page: > > -r Restore (rebuild a file system). The target file system > should > be made pristine with newfs(8), mounted and the user cd'd > into > the pristine file system before starting the restoration > of the > initial level 0 backup. These warnings are due to the way dump handles files which are hard linked to each other. Basicly, the dump format simply archives the inode # used by a hard-linked file, and restore depends on being able to use that same inode # when extracting a tree of files where some of them are hard-linked to each other. If you restore to a clean filesystem which was freshly newfs'ed, restore doesn't have to worry about the inodes it wants to use already being used by other files. -- -Chuck