DrKK
FreeNAS Generalissimo
- Joined
- Oct 15, 2013
- Messages
- 3,630
What do we think of this.
Exhibit A1:
Exhibit A2:
And this SSD, as outlined in exhibit A1|2, is a single drive vdev called "ssd", that I use for my jails. Exhibit B:
But then (and observe that the gptid matches exhibit B, so I am not pulling a fast one on you, Exhibit C:
You can see that ashift = 12. i.e., sector size is 4096, even though Exhibit A suggests the sector size is 512 (and that's BOTH physical and logical sector size, so there's no hocuspocus).
This *IS* a problem, right, and explains the ridiculous constant activity on my SSD (esp. deletes) that has been perplexing me for awhile? Yes or no?
I should blow this pool away and start it over with the correct ashift? yes or no? FreeNAS should have done this right in the first place? yes or no?
That is all.
Exhibit A1:
Code:
[root@daneel] ~# smartctl -a /dev/ada1 | grep -i model Model Family: Intel 53x and Pro 2500 Series SSDs Device Model: INTEL SSDSC2BW240H6
Exhibit A2:
Code:
[root@daneel] ~# smartctl -a /dev/ada1 | grep -i 'sector size' Sector Size: 512 bytes logical/physical
And this SSD, as outlined in exhibit A1|2, is a single drive vdev called "ssd", that I use for my jails. Exhibit B:
Code:
[root@daneel] ~# zpool status ssd pool: ssd state: ONLINE scan: scrub repaired 0 in 0h2m with 0 errors on Wed May 24 06:02:03 2017 config: NAME STATE READ WRITE CKSUM ssd ONLINE 0 0 0 gptid/d0cb19ce-1955-11e6-9094-002590d275c2 ONLINE 0 0 0 errors: No known data errors
But then (and observe that the gptid matches exhibit B, so I am not pulling a fast one on you, Exhibit C:
Code:
[root@daneel] ~# zdb -U /data/zfs/zpool.cache ssd: version: 5000 name: 'ssd' state: 0 txg: 6638241 pool_guid: 877894050773353097 hostid: 128484426 hostname: '' vdev_children: 1 vdev_tree: type: 'root' id: 0 guid: 877894050773353097 children[0]: type: 'disk' id: 0 guid: 11729960411399581475 path: '/dev/gptid/d0cb19ce-1955-11e6-9094-002590d275c2' whole_disk: 1 metaslab_array: 35 metaslab_shift: 31 ashift: 12 asize: 237905117184 is_log: 0 create_txg: 4 features_for_read: com.delphix:hole_birth com.delphix:embedded_data
You can see that ashift = 12. i.e., sector size is 4096, even though Exhibit A suggests the sector size is 512 (and that's BOTH physical and logical sector size, so there's no hocuspocus).
This *IS* a problem, right, and explains the ridiculous constant activity on my SSD (esp. deletes) that has been perplexing me for awhile? Yes or no?
I should blow this pool away and start it over with the correct ashift? yes or no? FreeNAS should have done this right in the first place? yes or no?
That is all.