Re: problem adding subdisk to vinum
On Tue, Aug 12, 2003 at 09:40:49AM -0700, Shawn Ostapuk wrote: 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: emptyPO: 1023 GB Size:149 GB vinum0.p0.s10 is at PO 1023G - reaching over the 1TByte limit on FreeBSD 4.x. That is because block numbers are signed 32 bit values. You need 5.x for volumes of this size. I'm not shure how the limit could result in this kind of symptom, but it won't work anyway and debugging this case can only change symptoms. Either use 5.x or be happy with your nearly 1T volume and start a new one for the next disk. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem adding subdisk to vinum
On Wednesday, 20 August 2003 at 15:37:27 -0700, Shawn Ostapuk wrote: Hmm. This is very strange. Try this: # vinum debug 8 # fsck ... # vinum info -V I'd like to see the output of the info command. Nothing :( su-2.03# vinum debug 8 su-2.03# fsck /dev/vinum/pr0n ** /dev/vinum/pr0n CANNOT READ: BLK 16 CONTINUE? [yn] n su-2.03# vinum info -V Flags: 0x80204 Total of 16 blocks malloced, total memory: 12400 Maximum allocs: 19, malloc table at 0xc0302ac0 0 requests active, maximum 1 active Time Event BufDev OffsetBytes SD SDoff Doffset Goffset I also tried it with the orig config, and when i mounted it I did get alot of data.. Time Event BufDev OffsetBytes SD SDoff Doffset Goffset 08:39:12.293806 1VS Write 0xcc91572c91.0 0x6ce78bf08192 08:39:12.293822 2LR Write 0xcc91572c91.0 0x6ce78bf08192 08:39:12.293827 3RQ Write 0xcc91572c116.6040x12f8 8192 9 11ef 0 0 08:39:12.294222 4DN Write 0xcc91572c116.6040x12f8 8192 9 11ef 0 0 08:39:12.294264 1VS Write 0xcc91587891.0 0x6ce78c008192 etc, for pages. If you can't be bothered sending me what I asked for, sorry, I can't help. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: problem adding subdisk to vinum
On Wednesday, 13 August 2003 at 19:03:21 -0700, Shawn Ostapuk wrote: su-2.03# vinum lv -r V pr0n State: up Plexes: 1 Size: 1172 GB ... Either method results in an umountable and unaccessable filesystem. su-2.03# mount /dev/vinum/pr0n /data mount: /dev/vinum/pr0n on /data: incorrect super block su-2.03# fsck /dev/vinum/pr0n ** /dev/vinum/pr0n CANNOT READ: BLK 16 CONTINUE? [yn] ^C That's with the states shown above? Really? Are there any log messages? Yes with the states shown above. The above is a copy and paste of successive commands i went through for the email response :) No errors are reported to console, stderr, or any of the log files in /var/log/ including messages. Hmm. This is very strange. Try this: # vinum debug 8 # fsck ... # vinum info -V I'd like to see the output of the info command. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: problem adding subdisk to vinum
On Tuesday, 12 August 2003 at 9:40:49 -0700, Shawn Ostapuk wrote: 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 ... Hmm, that plex shouldn't have been corrupt. But plex states are pretty meaningless anyway. 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.s10 State: emptyPO: 1023 GB Size:149 GB the old filesystem is not accessable at this point. invalid superblock and other errors with fsck and growfs. That's the kind of message I'd want to see. But given that the subdisk isn't available, that's not surprising. after chanigng the state to up setstate up vinum0.p0.s10, the behaviour would also be the same. Really? Then I definitely want to see it. (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) It's best to check this. It shouldn't be up immediately. 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. That's not the issue. The real question is the states. Getting states right is a black art, and it's possible that that's your real problem. 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. OK. Start from your last status (volume up, plex corrupt, last subdisk empty). Set plex and last subdisk to up. Run fsck and tell me what you get. If that works, try growfs. If that workds, do a saveconfig. 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. Thanks. Thank you for your help as well. You're welcome. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: problem adding subdisk to vinum
On Tuesday, 12 August 2003 at 23:52:09 -0700, Shawn Ostapuk wrote: (Sorry for being so long, thought it would be less confusing and save additional questions to show complete vinum lists) At this point lv -r shows everything as up. same as above but with total size as 1172 GB. vinum list _looks_ perfect. su-2.03# vinum lv -r V pr0n State: up Plexes: 1 Size: 1172 GB P vinum0.p0 C State: up Subdisks:11 Size: 1172 GB S vinum0.p0.s00 State: up PO:0 B Size:152 GB S vinum0.p0.s01 State: up PO: 152 GB Size: 28 GB S vinum0.p0.s02 State: up PO: 181 GB Size: 76 GB S vinum0.p0.s03 State: up PO: 257 GB Size: 76 GB S vinum0.p0.s04 State: up PO: 333 GB Size: 76 GB S vinum0.p0.s05 State: up PO: 410 GB Size: 76 GB S vinum0.p0.s06 State: up PO: 486 GB Size: 76 GB S vinum0.p0.s07 State: up PO: 562 GB Size: 74 GB S vinum0.p0.s08 State: up PO: 637 GB Size:233 GB S vinum0.p0.s08 State: up PO: 637 GB Size:233 GB S vinum0.p0.s09 State: up PO: 871 GB Size:152 GB S vinum0.p0.s10 State: up PO: 1023 GB Size:149 GB Either method results in an umountable and unaccessable filesystem. su-2.03# mount /dev/vinum/pr0n /data mount: /dev/vinum/pr0n on /data: incorrect super block su-2.03# fsck /dev/vinum/pr0n ** /dev/vinum/pr0n CANNOT READ: BLK 16 CONTINUE? [yn] ^C That's with the states shown above? Really? Are there any log messages? OK. Start from your last status (volume up, plex corrupt, last subdisk empty). Set plex and last subdisk to up. Run fsck and tell me what you get. If that works, try growfs. If that workds, do a saveconfig. I've probably added the new disk over 100 times now trying every possible option. ... Despite all this, it still looks like pilot error to me. Are you very sure that every object in your volume was up when you tried that fsck? Are they still up afterwards? No log messages? Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
re: problem adding subdisk to vinum
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: emptyPO: 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
