replaced ancient 1068E with SAS 2308 chipset and all is well. Thanks! (I rather dislike the ultra long disk names that result from the good old c0t0d0 , but that's life)
happily, I didn't even have to rebuild the zpool and the mdb output looks as expected. On Sun, Aug 23, 2015 at 5:36 PM, Doug Hughes <d...@will.to> wrote: > I do suspect that there is a problem with the card and the 2TB/4TB. Still, > shouldn't my sd.conf entries result in zdb showing ashift=12 and mdb > showing block size 0x1000? > > (the comma issue, in answer to other person, is ok. This is not the last > entry in sd.conf) > > > > On 8/23/2015 6:20 AM, Alexander Lesle wrote: > >> Hello Doug Hughes and List, >> >> I use the same HGST drive and they have all 4 TB capacity in my pools. >> >> ,-----[ ]----- >> | >> | AVAILABLE DISK SELECTIONS: >> | 0. c2t0d0 <VMware-Virtualdisk-1.0 cyl 5012 alt 2 hd 224 sec 56> >> | /pci@0,0/pci15ad,1976@10/sd@0,0 >> | 1. c2t1d0 <VMware-Virtualdisk-1.0 cyl 5012 alt 2 hd 224 sec 56> >> | /pci@0,0/pci15ad,1976@10/sd@1,0 >> | 2. c4t5000CCA23DCCC6BCd0 <ATA-HGST HDS724040AL-A580-3.64TB> >> | /scsi_vhci/disk@g5000cca23dccc6bc >> | 3. c4t5000CCA23DCD21A4d0 <ATA-HGST HDS724040AL-A580-3.64TB> >> | /scsi_vhci/disk@g5000cca23dcd21a4 >> | 4. c4t5000CCA23DCD25A1d0 <ATA-HGST HDS724040AL-A580-3.64TB> >> | /scsi_vhci/disk@g5000cca23dcd25a1 >> | Specify disk (enter its number): >> | >> `------------------- >> >> When you wrote only one item in sd.conf you must write a ; and not , >> at last letter. >> But this HDD you must not list in sd.conf it will present ashift=12. >> >> ,-----[ ]----- >> | >> | root@aio:/root# zdb -C >> | pool_aio: >> | version: 5000 >> | name: 'pool_aio' >> | state: 0 >> | txg: 5222458 >> | pool_guid: 11088269185580178933 >> | hostid: 720590413 >> | hostname: 'aio' >> | vdev_children: 1 >> | vdev_tree: >> | type: 'root' >> | id: 0 >> | guid: 11088269185580178933 >> | children[0]: >> | type: 'mirror' >> | id: 0 >> | guid: 1388041250297859353 >> | metaslab_array: 33 >> | metaslab_shift: 35 >> | ashift: 12 >> | asize: 4000773570560 >> | is_log: 0 >> | create_txg: 4 >> | children[0]: >> | type: 'disk' >> | id: 0 >> | guid: 18178429901005250887 >> | path: '/dev/dsk/c4t5000CCA23DCCC6BCd0s0' >> | devid: 'id1,sd@n5000cca23dccc6bc/a' >> | phys_path: '/scsi_vhci/disk@g5000cca23dccc6bc:a' >> | whole_disk: 1 >> | DTL: 45 >> | create_txg: 4 >> | children[1]: >> | type: 'disk' >> | id: 1 >> | guid: 12635800974590752762 >> | path: '/dev/dsk/c4t5000CCA23DCD21A4d0s0' >> | devid: 'id1,sd@n5000cca23dcd21a4/a' >> | phys_path: '/scsi_vhci/disk@g5000cca23dcd21a4:a' >> | whole_disk: 1 >> | DTL: 43 >> | create_txg: 4 >> | children[2]: >> | type: 'disk' >> | id: 2 >> | guid: 15588560262687738746 >> | path: '/dev/dsk/c4t5000CCA23DCD25A1d0s0' >> | devid: 'id1,sd@n5000cca23dcd25a1/a' >> | phys_path: '/scsi_vhci/disk@g5000cca23dcd25a1:a' >> | whole_disk: 1 >> | DTL: 41 >> | create_txg: 4 >> | features_for_read: >> | com.delphix:hole_birth >> | com.delphix:embedded_data >> | >> `------------------- >> ,-----[ ]----- >> | >> | root@aio:/root# zdb | egrep 'ashift| name' >> | name: 'pool_aio' >> | ashift: 12 >> | name: 'rpool' >> | ashift: 9 >> | >> `------------------- >> >> I think its a hardware issue. >> Test this what Michael Talbott wrote. >> >> On August, 22 2015, 23:49 <Doug Hughes> wrote in [1]: >> >> I'm following this page: >>> http://wiki.illumos.org/display/illumos/ZFS+and+Advanced+Format+disks >>> but I just can't get my HGST 4K disks to get the 4TB capacity in the >>> zpool. >>> I've cross referenced and verified multiple times and this should work >>> for sd_config_list= >>> "ATA HGST HDS724040AL", "physical-block-size:4096", >>> >> >
_______________________________________________ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss