Date: Wed, 06 Sep 2006 09:46:59 -0700 From: Paul Saab <ps@freebsd.org> To: Bucky Jordan <bjordan@lumeta.com> Cc: Jeffrey Williams <jeff@sailorfej.net>, dmartin@euitt.upm.es, freebsd-stable@FreeBSD.org, freebsd-i386@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: i386/100160: [mfid] Perc5i: additional symptomatic info on virtual disk detection issue Message-ID: <44FEFB83.3010102@freebsd.org> In-Reply-To: <78ED28FACE63744386D68D8A9D1CF5D4104C43@MAIL.corp.lumeta.com> References: <78ED28FACE63744386D68D8A9D1CF5D4104C43@MAIL.corp.lumeta.com>
next in thread | previous in thread | raw e-mail | index | archive | help
revision 1.11 date: 2006/06/20 22:41:44; author: ps; state: Exp; lines: +77 -202 Instead of using scsi probes to do device discovery, use the firmware commands to grab the device listing. This resolves issues using multiple volumes, where each volume was actually internally pointing to target 0. Bucky Jordan wrote: >> In the meantime if anybody else is aware of another work around of fix >> for this, I appreciate hearing about it. >> > > I've got almost the same setup- 6.1 amd64 RELEASE, a 2950 with 6 drives > attached to the Perc5/I SAS Raid controller. Right now I've got the > whole thing configured as a RAID5x6 disks and it seems to be working > fine. > > I was able to also create smaller RAID sets (for example, a 4 disk > RAID10) without an issue, and I did not have to remove extra drives. > > Someone (on -hardware I think) mentioned that the problem recognizing > multiple virtual volumes is addressed in 6-stable, but I have not had > the chance to try it out. I will post the results if/when I do. > > - Bucky > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44FEFB83.3010102>