Hello, FreeBSD Current. Have some trouble with adding SSD drive as secondarycache device on 10.0-CURRENT FreeBSD 10.0-CURRENT #1 r255173 : SSD INTEL SSDSC2BW180A4
dmesg: ada1 at ahcich2 bus 0 scbus4 target 0 lun 0 ada1: <INTEL SSDSC2BW180A4 DC02> ATA-9 SATA 3.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 171705MB (351651888 512 byte sectors: 16H 63S/T 16383C) ada1: quirks=0x1<4K> ada1: Previously was known as ad8 # diskinfo -v /dev/ada1 /dev/ada1 512 # sectorsize 180045766656 # mediasize in bytes (167G) 351651888 # mediasize in sectors 4096 # stripesize 0 # stripeoffset 348861 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. BTDA326504N51802GN # Disk ident. Creating partition and adding: # gpart create -s gpt ada1 # gpart add -t freebsd-zfs -s3G -l zil0 ada1 # gpart add -t freebsd-zfs -l cache0 ada1 # zpool add disk1 log /dev/gpt/zil0 # zpool add disk1 cache /dev/gpt/cache0 After that have: log gpt/zil0 ONLINE 0 0 0 cache gpt/cache0 ONLINE 0 0 0 block size: 512B configured, 4096B native But why? ZFS can't properly set sector size for cache device (quirks=0x1<4K>)? And have some strange behavior with ZIl partition on the same SSD - everything works! Okay, was trying to do some workaround with GNOP: # gnop create -S4096 /dev/gpt/cache0 # zpool add disk1 cache /dev/gpt/cache0.nop Seems to be OK cache gpt/cache0.nop ONLINE 0 0 0 But after reboot pool has status:One or more devices are configured to use a non-native block size. Expect reduced performance. cache gptid/39e40c33-1c4d-11e3-ac20-002590aa9548 ONLINE 0 0 0 block size: 512B configured, 4096B native And no gnop parts was found, and even gpart (in /dev/gpart) # gnop status # gnop: Command 'status' not available. # gpart show -l ada1 => 34 351651821 ada1 GPT (167G) 34 6 - free - (3.0k) 40 6291456 1 zil0 (3.0G) 6291496 345360352 2 cache0 (164G) 351651848 7 - free - (3.5k) # ls /dev/gpt/cache* zsh: no matches found: /dev/gpt/cache* Please, help to deal with this problem. Or what else information can be useful to find out this trouble. _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
