Date: Sun, 2 May 1999 16:36:30 +0930 From: Greg Lehey <grog@lemis.com> To: Jacques Vidrine <n@nectar.com> Cc: freebsd-questions@freebsd.org Subject: Re: vinum-- resizing disks Message-ID: <19990502163630.K80561@freebie.lemis.com> In-Reply-To: <19990502070142.2AEF11DD7@spawn.nectar.com>; from Jacques Vidrine on Sun, May 02, 1999 at 02:01:41AM -0500 References: <19990501210026.357911DC5@spawn.nectar.com> <19990502120821.W80561@freebie.lemis.com> <19990502070142.2AEF11DD7@spawn.nectar.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[Format recovered--see http://www.lemis.com/email/email-format.html] On Sunday, 2 May 1999 at 2:01:41 -0500, Jacques Vidrine wrote: > On 2 May 1999 at 12:08, Greg Lehey <grog@lemis.com> 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. >> 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. > > 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. OK, a couple of things: first, check the size of the drive. It should be 17655372 sectors, and not 9430092. Then you could have done an fsck, but it looks as if you're beyond that. Good to hear that it worked. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990502163630.K80561>