Date: Tue, 12 Aug 2003 09:40:49 -0700 From: Shawn Ostapuk <flagg@slumber.org> To: freebsd-questions@freebsd.org Subject: re: problem adding subdisk to vinum Message-ID: <20030812164049.GA5490@slumber.org>
next in thread | raw e-mail | index | archive | help
> Vinum configs are additive. You shouldn't redefine things that Vinum > already knows about. As far as I can see with a superficial look, all > you need is: > > > drive vinumdrive10 device /dev/ad7e > > sd name vinum0.p0.s10 drive vinumdrive10 size 0 plex vinum0.p0 Thanks, I'll remember that in the future, for now that did not fix the problem. > > BUT, now i cant mount the old filesystem > > > > mount says invalid superblock, fsck says cant read block (and -b32, > > says same thing, ad nauseum), and growfs also errors out. > > Looks like you added the subdisk in the wrong place. What does vinum > lv -r pr0n say? before: su-2.03# vinum lv -r pr0n V pr0n State: up Plexes: 1 Size: 1172 GB P vinum0.p0 C State: corrupt Subdisks: 11 Size: 1172 GB S vinum0.p0.s0 State: up PO: 0 B Size: 152 GB S vinum0.p0.s1 State: up PO: 152 GB Size: 28 GB S vinum0.p0.s2 State: up PO: 181 GB Size: 76 GB S vinum0.p0.s3 State: up PO: 257 GB Size: 76 GB S vinum0.p0.s4 State: up PO: 333 GB Size: 76 GB S vinum0.p0.s5 State: up PO: 410 GB Size: 76 GB S vinum0.p0.s6 State: up PO: 486 GB Size: 76 GB S vinum0.p0.s7 State: up PO: 562 GB Size: 74 GB S vinum0.p0.s8 State: up PO: 637 GB Size: 233 GB S vinum0.p0.s9 State: up PO: 871 GB Size: 152 GB after: su-2.03# cat /etc/vinum.conf.new drive vinumdrive10 device /dev/ad7e sd name vinum0.p0.s10 drive vinumdrive10 size 0 plex vinum0.p0 su-2.03# vinum create /etc/vinum.conf.new .. V pr0n State: up Plexes: 1 Size: 1172 GB P vinum0.p0 C State: corrupt Subdisks: 11 Size: 1172 GB S vinum0.p0.s0 State: up PO: 0 B Size: 152 GB S vinum0.p0.s1 State: up PO: 152 GB Size: 28 GB S vinum0.p0.s2 State: up PO: 181 GB Size: 76 GB S vinum0.p0.s3 State: up PO: 257 GB Size: 76 GB S vinum0.p0.s4 State: up PO: 333 GB Size: 76 GB S vinum0.p0.s5 State: up PO: 410 GB Size: 76 GB S vinum0.p0.s6 State: up PO: 486 GB Size: 76 GB S vinum0.p0.s7 State: up PO: 562 GB Size: 74 GB S vinum0.p0.s8 State: up PO: 637 GB Size: 233 GB S vinum0.p0.s9 State: up PO: 871 GB Size: 152 GB S vinum0.p0.s10 State: empty PO: 1023 GB Size: 149 GB the old filesystem is not accessable at this point. invalid superblock and other errors with fsck and growfs. after chanigng the state to up "setstate up vinum0.p0.s10", the behaviour would also be the same. (i am still unsure as to the empty state it says, as the man page says that if adding a subdisk to a plex to a volume that has no other plex's it would bring the state to up immediately. (i am also not positive at this point the state was always set to empty, i believe at least a few times it did come up with State: up) also, i have more than double verified the drive in the right place and is functioning. after having trouble i even re-fdisk'd the new drive (ad7e) and newfs's it resulting in zero errors or problems. the bios detects it quickly with no delays as well. > > > from what i gathered appending a drive to the existing vinum config > > should not have any effect on the existing filesystem size/data, > > etc. i should be able to at the very least access it without any > > problems i believe. > > Correct, modulo the fact that you've redefined a number of objects. > It's possible that you're tickling a bug in the process. It seems to have the same trouble even trying with the new configuration above where i simply append the config intead of resetconfig/create -f. If you have any other suggestions it would help alot, i've been going nuts for days now trying to get this new drive added -- normally a simple process. Also let me say vinum (until now) has worked wonderfully for me. I've been using it for years and have never lost a single byte of data due to any vinum problems, I trust it with my most important data and sleep soundly at nite. Wonderful tool. Thank you for your help as well. shawn.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030812164049.GA5490>