Re: vinum raid5: newfs throws an error
Greg 'groggy' Lehey writes: There was once an error in the stripe size calculations that meant that there were holes in the plexes. Maybe it's still there (old Vinum is not being maintained). But you should have seen that in the console messages at create time. Vinum reports the disk sizes as 17500MB (da1) and 17359MB (da2, da3). The raid5 volume and plex have a size of 33GB. This looks like the kind of scenario where that could happen. Try this: 1. First, find a better stripe size. It shouldn't be a power of 2, but it should be a multiple of 16 kB. I'd recommend 496 kB. This won't fix the problem, but it's something you should do anyway 2. Calculate the length of an exact number of stripes, and create the subdisks in that length. Try again and see what happens. 3. Use gvinum instead of vinum and try both ways. Ok, I decreased the stripe size to 496, regardless of whether it has anything to do with my problem. Next I set the subdisk length to 17359m on all disks, and things started to work ok. No more newfs errors here. Before doing this I also had a brief encounter with gvinum. There is no manpage in 5.3BETA7, so I assumed it groks the same config files as vinum. However, this did not do me any good as it simply rebooted the box. I guess gvinum works better in RELEASE. Thanks a lot for your help. Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with mhoenicka) http://www.mhoenicka.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum raid5: newfs throws an error
On Monday, 6 December 2004 at 23:44:59 +0100, Markus Hoenicka wrote: Greg 'groggy' Lehey writes: There was once an error in the stripe size calculations that meant that there were holes in the plexes. Maybe it's still there (old Vinum is not being maintained). But you should have seen that in the console messages at create time. Vinum reports the disk sizes as 17500MB (da1) and 17359MB (da2, da3). The raid5 volume and plex have a size of 33GB. This looks like the kind of scenario where that could happen. Try this: 1. First, find a better stripe size. It shouldn't be a power of 2, but it should be a multiple of 16 kB. I'd recommend 496 kB. This won't fix the problem, but it's something you should do anyway 2. Calculate the length of an exact number of stripes, and create the subdisks in that length. Try again and see what happens. 3. Use gvinum instead of vinum and try both ways. Ok, I decreased the stripe size to 496, regardless of whether it has anything to do with my problem. Next I set the subdisk length to 17359m on all disks, and things started to work ok. No more newfs errors here. OK, looks like this was the hole in the plex issue. I thought that was gone. 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. pgpn7akcOjP72.pgp Description: PGP signature
Re: vinum raid5: newfs throws an error
On Monday, 6 December 2004 at 3:05:31 +0100, Markus Hoenicka wrote: Hi all, now that I can use the full capacity of my disks, I'm stuck again. I'm trying to set up a raid5 from three SCSI disks (I know that a serious raid5 should use five disks or more, but I have to make do with three at the moment). The configuration is as follows: drive ibma device /dev/da1s1e drive ibmb device /dev/da2s1e drive ibmc device /dev/da3s1e volume raid5 setupstate plex org raid5 512k sd length 0m drive ibma sd length 0m drive ibmb sd length 0m drive ibmc This works ok. Then I run vinum init to initialize the drives. Trying to create a filesystem on this construct results in the error message: newfs: wtfs: 65536 bytes at sector 71130688: Input/output error Is that trying to tell me that my calculation of the group size is incorrect? Does it have to do anything with the fact that the three disks have slightly different capacities? There was once an error in the stripe size calculations that meant that there were holes in the plexes. Maybe it's still there (old Vinum is not being maintained). But you should have seen that in the console messages at create time. Vinum reports the disk sizes as 17500MB (da1) and 17359MB (da2, da3). The raid5 volume and plex have a size of 33GB. This looks like the kind of scenario where that could happen. Try this: 1. First, find a better stripe size. It shouldn't be a power of 2, but it should be a multiple of 16 kB. I'd recommend 496 kB. This won't fix the problem, but it's something you should do anyway 2. Calculate the length of an exact number of stripes, and create the subdisks in that length. Try again and see what happens. 3. Use gvinum instead of vinum and try both ways. 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. pgpRINJrCFKRb.pgp Description: PGP signature
