On Monday, 10 February 2003 at 23:11:02 -0500, Pete wrote: > On Mon, 03 Feb 2003, Pete wrote: > >> On Mon, 03 Feb 2003, Greg 'groggy' Lehey wrote: >> >>> On Sunday, 2 February 2003 at 13:50:20 -0500, Pete wrote: >>>> What does this mean? Whichever drive is last, that's the one I cannot >>>> "disklabel -e" to set its fstype to "vinum". >>> >>> There must be some other reason for that. Do you have any disk label >>> at all? >> >> Yes, it does. I can even mount /dev/ar2e because I had created a disk >> label on it when it was attached as /dev/ar1 previously. >> >> The problem seems to be accessing /dev/ar2 with disklabel. I've swapped >> cables and cards. I'm even currently using two cards (one ATA100 and >> ATA133). I've swapped the drives all around and the only constant >> factor seems to be ar2. With all three drives on one card (two master >> and one slave) or spread between the two cards (all three masters), as >> long as there were three drives, /dev/ar2 would be like this. >> >> Is the ar driver only limited to two devices? > > So it seems that there's a problem with more than two /dev/ar devices, > or at least more than two Promise-based /dev/ar devices. Does anyone > know more about this or should I take this to freebsd-hackers?
Hmm, yes, that's a possibility. -hackers won't help you there, but a bug report might. 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
Description: PGP signature