From owner-freebsd-questions Sun May 2 0: 1:54 1999 Delivered-To: freebsd-questions@freebsd.org Received: from sakaki.communique.net (sakaki.communique.net [204.27.64.202]) by hub.freebsd.org (Postfix) with ESMTP id 97D3314C9D for ; Sun, 2 May 1999 00:01:52 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by sakaki.communique.net (8.8.8/8.8.8) with ESMTP id CAA08345; Sun, 2 May 1999 02:01:51 -0500 (CDT) Received: from spawn.nectar.com (spawn.nectar.com [10.0.0.101]) by cerebus.nectar.com (Postfix) with ESMTP id 49E1711D; Sun, 2 May 1999 02:01:50 -0500 (CDT) Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (Postfix) with ESMTP id 2AEF11DD7; Sun, 2 May 1999 02:01:42 -0500 (CDT) X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt From: Jacques Vidrine To: Greg Lehey Cc: freebsd-questions@freebsd.org In-reply-to: <19990502120821.W80561@freebie.lemis.com> References: <19990501210026.357911DC5@spawn.nectar.com> <19990502120821.W80561@freebie.lemis.com> Subject: Re: vinum-- resizing disks Date: Sun, 02 May 1999 02:01:41 -0500 Message-Id: <19990502070142.2AEF11DD7@spawn.nectar.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, what do you know, it appears to have worked. Nifty! I say ``appears'' because I haven't found anything wrong yet, but I'm reading through the filesystems with ``tar -cf /dev/null'' to make sure I touch everything I had. Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org On 2 May 1999 at 12:08, Greg Lehey wrote: > On Saturday, 1 May 1999 at 16:00:25 -0500, Jacques Vidrine wrote: > > Hi, > > > > After running for a couple of months with about half of my storage > > space under vinum, I am happy enough with the results to wish to move > > all my storage to vinum volumes. (Great work Greg!) In order to do > > so, I'll need to resize the vinum disk objects, and I wonder if that > > is possible. > > > > Each drive on my system is partitioned into a-f (for on which I have > > swap and UFS filesystems), and h (which I use for vinum). e.g. > > > > 8 partitions: > > # size offset fstype [fsize bsize bps/cpg] > > a: 128520 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 7) > > b: 128520 128520 swap # (Cyl. 8 - 15) > > c: 17912412 0 unused 0 0 # (Cyl. 0 - 1114 *) > > e: 4112640 257040 4.2BSD 1024 8192 8192 # (Cyl. 16 - 271) > > f: 4112640 4369680 4.2BSD 1024 8192 8192 # (Cyl. 272 - 527) > > h: 9430092 8482320 vinum # (Cyl. 528 - 1114 *) > > > > Now, I wonder can I backup partions e and f, delete them, and then resize > > h to allocate the storage to vinum? e.g. I want to wind up with: > > > > 8 partitions: > > # size offset fstype [fsize bsize bps/cpg] > > a: 128520 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 7) > > b: 128520 128520 swap # (Cyl. 8 - 15) > > c: 17912412 0 unused 0 0 # (Cyl. 0 - 1114 *) > > h: 17655372 257040 vinum 1024 8192 8192 # (Cyl. 16 - 1114 *) > > > > I imagine that I'm just going to have to back everything up and > > start over, but I thought I'd ask first. > > Well, I can think of a way, but I can't guarantee it'll work, so it's > best to do a backup first anyway. You could move the data on disk. > Once you've done your backups, create the following disk label: > > > 8 partitions: > > # size offset fstype [fsize bsize bps/cpg] > > a: 128520 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 7) > > b: 128520 128520 swap # (Cyl. 8 - 15) > > c: 17912412 0 unused 0 0 # (Cyl. 0 - 1114 *) > > e: 17655372 257040 vinum # (Cyl. 16 - 1114 *) > > h: 9430092 8482320 vinum # (Cyl. 528 - 1114 *) > > Then do dd if=/dev/rda1h of=/dev/rda1e to move the data. After that, > you can delete partition h (and rename e to h if you want), restart > Vinum, and you *may* find that you still have your information. From > what I see in the code, it should automatically adapt to the bigger > drive. Whatever you do, though, don't leave the overlapping Vinum > partition at offset 8482320 there; Vinum will open both of them, > updating the config information, and you'll end up with data > corruption in the partition starting at 257040. > > If you try this, please let me know the outcome. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message