Date: Sun, 15 Jul 2007 09:45:15 +0200 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Aaron Hurt <aaron@goflexitllc.com> Cc: freebsd-fs@freebsd.org Subject: Re: gconcat incorrect superblock after adding a disk Message-ID: <20070715074515.GA9823@garage.freebsd.pl> In-Reply-To: <46997CC3.3030405@goflexitllc.com> References: <46997CC3.3030405@goflexitllc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 14, 2007 at 08:47:47PM -0500, Aaron Hurt wrote: > I have a fairly decent sized gconcat array composed of 4 disks (ad8 ad10 > ad12 ad14) the previous working members. Recently I tried to add > another disk using the following procedure: > > umount /dev/concat/store1 > gconcat stop store1 > gconcat label store1 ad8 ad10 ad12 ad14 ad4 > growfs /dev/concat/store1 > > ..... it was at this point that I got the incorrect superblock error > after adding ad4. Now, even if I try to remove ad4 and label with the > original disks (keeping the original order) it still will not mount or > fsck. The exact messages are below: > > schroder# mount /dev/concat/store1 /store > mount: /dev/concat/store1 on /store: incorrect super block Your data should be safe if you didn't write anything into the disks yet and growfs(8) didn't corrupt your file system somehow. Gconcat itself won't touch your data - the only thing it does is to write into last disk's sector. Are you sure you used exactly the same order as you had used when you created concatenated device without ad4 disk? Growfs finished sucessfully? > Geom name: store1 > State: UP > Status: Total=4, Online=4 > Type: AUTOMATIC > ID: 1480896172 > Providers: > 1. Name: concat/store1 > Mediasize: 640167540736 (596G) > Sectorsize: 512 > Mode: r0w0e0 > Consumers: > 1. Name: ad8 > Mediasize: 120034123776 (112G) > Sectorsize: 512 > Mode: r0w0e0 > Start: 0 > End: 120034123264 > 2. Name: ad10 > Mediasize: 200049647616 (186G) > Sectorsize: 512 > Mode: r0w0e0 > Start: 120034123264 > End: 320083770368 > 3. Name: ad12 > Mediasize: 160041885696 (149G) > Sectorsize: 512 > Mode: r0w0e0 > Start: 320083770368 > End: 480125655552 > 4. Name: ad14 > Mediasize: 160041885696 (149G) > Sectorsize: 512 > Mode: r0w0e0 > Start: 480125655552 > End: 640167540736 If this is from before you added ad4, then the order is correct. > schroder# fdisk /dev/concat/store1 > ******* Working on device /dev/concat/store1 ******* > parameters extracted from in-core disklabel are: > cylinders=77829 heads=255 sectors/track=63 (16065 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=77829 heads=255 sectors/track=63 (16065 blks/cyl) > > fdisk: invalid fdisk partition table found > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 63, size 1250322822 (610509 Meg), flag 80 (active) > beg: cyl 0/ head 1/ sector 1; > end: cyl 4/ head 254/ sector 63 > The data for partition 2 is: > <UNUSED> > The data for partition 3 is: > <UNUSED> > The data for partition 4 is: > <UNUSED> You have a slice there? You extended /dev/concat/store1, not /dev/concat/store1s1. Where is you file system? On store1, store1s1, store1s1a? -- Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070715074515.GA9823>