Date: Sat, 24 Jul 2010 11:50:03 -0700 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Dan Langille <dan@langille.org> Cc: freebsd-stable@freebsd.org Subject: Re: Using GTP and glabel for ZFS arrays Message-ID: <20100724185003.GA96773@icarus.home.lan> In-Reply-To: <4C4B1106.8070402@langille.org> References: <AANLkTimbYGpC0aYGnE61J5ZopQVD9m8hrz07CZAnsvsq@mail.gmail.com> <AANLkTikwNEXpTz-hpKLta0T3Lx67nRHtOaVLp_c7C8BI@mail.gmail.com> <4C47E610.2040409@langille.org> <4C47EC47.5090000@yandex.ru> <4C47ED09.7020808@langille.org> <alpine.OSX.2.00.1007220327170.33454@hotlap.local> <4C47F4F1.8030804@langille.org> <alpine.OSX.2.00.1007220357570.33454@hotlap.local> <4C47FD18.7030002@langille.org> <4C4B1106.8070402@langille.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 24, 2010 at 12:12:54PM -0400, Dan Langille wrote: > On 7/22/2010 4:11 AM, Dan Langille wrote: > >On 7/22/2010 4:03 AM, Charles Sprickman wrote: > >>On Thu, 22 Jul 2010, Dan Langille wrote: > >> > >>>On 7/22/2010 3:30 AM, Charles Sprickman wrote: > >>>>On Thu, 22 Jul 2010, Dan Langille wrote: > >>>> > >>>>>On 7/22/2010 2:59 AM, Andrey V. Elsukov wrote: > >>>>>>On 22.07.2010 10:32, Dan Langille wrote: > >>>>>>>I'm not sure of the criteria, but this is what I'm running: > >>>>>>> > >>>>>>>atapci0:<SiI 3124 SATA300 controller> port 0xdc00-0xdc0f mem > >>>>>>>0xfbeffc00-0xfbeffc7f,0xfbef0000-0xfbef7fff irq 17 at device 4.0 on > >>>>>>>pci7 > >>>>>>> > >>>>>>>atapci1:<SiI 3124 SATA300 controller> port 0xac00-0xac0f mem > >>>>>>>0xfbbffc00-0xfbbffc7f,0xfbbf0000-0xfbbf7fff irq 19 at device 4.0 on > >>>>>>>pci3 > >>>>>>> > >>>>>>>I added ahci_load="YES" to loader.conf and rebooted. Now I see: > >>>>>> > >>>>>>You can add siis_load="YES" to loader.conf for SiI 3124. > >>>>> > >>>>>Ahh, thank you. > >>>>> > >>>>>I'm afraid to do that now, before I label my ZFS drives for fear that > >>>>>the ZFS array will be messed up. But I do plan to do that for the > >>>>>system after my plan is implemented. Thank you. :) > >>>> > >>>>You may even get hotplug support if you're lucky. :) > >>>> > >>>>I just built a box and gave it a spin with the "old" ata stuff and then > >>>>with the "new" (AHCI) stuff. It does perform a bit better and my BIOS > >>>>claims it supports hotplug with ahci enabled as well... Still have to > >>>>test that. > >>> > >>>Well, I don't have anything to support hotplug. All my stuff is > >>>internal. > >>> > >>>http://sphotos.ak.fbcdn.net/hphotos-ak-ash1/hs430.ash1/23778_106837706002537_100000289239443_171753_3508473_n.jpg > >>> > >>> > >> > >>The frankenbox I'm testing on is a retrofitted 1U (it had a scsi > >>backplane, now has none). > >> > >>I am not certain, but I think with 8.1 (which it's running) and all the > >>cam integration stuff, hotplug is possible. Is a special backplane > >>required? I seriously don't know... I'm going to give it a shot though. > >> > >>Oh, you also might get NCQ. Try: > >> > >>[root@h21 /tmp]# camcontrol tags ada0 > >>(pass0:ahcich0:0:0:0): device openings: 32 > > > ># camcontrol tags ada0 > >(pass0:siisch2:0:0:0): device openings: 31 > > > >resending with this: > > > >ada{0..4} give the above. > > > ># camcontrol tags ada5 > >(pass5:ahcich0:0:0:0): device openings: 32 > > > >That's part of the gmirror array for the OS, along with ad6 which has > >similar output. > > > >And again with this output from one of the ZFS drives: > > > ># camcontrol identify ada0 > >pass0: <Hitachi HDS722020ALA330 JKAOA28A> ATA-8 SATA 2.x device > >pass0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > > > >protocol ATA/ATAPI-8 SATA 2.x > >device model Hitachi HDS722020ALA330 > >firmware revision JKAOA28A > >serial number JK1130YAH531ST > >WWN 5000cca221d068d5 > >cylinders 16383 > >heads 16 > >sectors/track 63 > >sector size logical 512, physical 512, offset 0 > >LBA supported 268435455 sectors > >LBA48 supported 3907029168 sectors > >PIO supported PIO4 > >DMA supported WDMA2 UDMA6 > >media RPM 7200 > > > >Feature Support Enable Value Vendor > >read ahead yes yes > >write cache yes yes > >flush cache yes yes > >overlap no > >Tagged Command Queuing (TCQ) no no > >Native Command Queuing (NCQ) yes 32 tags > >SMART yes yes > >microcode download yes yes > >security yes no > >power management yes yes > >advanced power management yes no 0/0x00 > >automatic acoustic management yes no 254/0xFE 128/0x80 > >media status notification no no > >power-up in Standby yes no > >write-read-verify no no 0/0x0 > >unload no no > >free-fall no no > >data set management (TRIM) no > > Does this support NCQ? Does *what* support NCQ? The output above, despite having lost its whitespace formatting, indicates the drive does support NCQ and due to using CAM (via ahci.ko or siis.ko) has NCQ in use: > >Native Command Queuing (NCQ) yes 32 tags A binary verification (does it/does it not) is also visible in your kernel log, ex: ada2: Command Queueing enabled -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100724185003.GA96773>