TrevorX
Explorer
- Joined
- Mar 10, 2015
- Messages
- 77
Hello,
I have a couple of questions. Firstly, I was of the understanding/belief that ZFS creates ZPools with 4096 bytes sector size by default, but I've just discovered that my array consisting of six HGST 6TB NAS drives is reporting 4096 bytes physical, but 512 bytes logical sector size. This is obviously sub-optimal and a little confusing. So I thought I'd ask:
1) Why would this be happening?
2) What will be the impact of leaving it as is? I realise the only way to fix it will be to rebuild the ZPool, and as I have around 12TB of data on there that's not really an option.
3) Even if I did decide to rebuild the ZPool, how would I ensure that it wouldn't create 512 byte sector size again, given that it shouldn't be able to do this anyway?
Investigating my second question is what led me to the discovery of the above issue. FreeNAS is reporting 8 currently unreadable sectors on one of its drives (/dev/ada7). But I've run through a long SMART test (smartctl -t long /dev/ada7) and it shows zero errors. So now what do I do? Pull the drive and manually secure erase it?
Thanks for your help,
Trevor
I have a couple of questions. Firstly, I was of the understanding/belief that ZFS creates ZPools with 4096 bytes sector size by default, but I've just discovered that my array consisting of six HGST 6TB NAS drives is reporting 4096 bytes physical, but 512 bytes logical sector size. This is obviously sub-optimal and a little confusing. So I thought I'd ask:
1) Why would this be happening?
2) What will be the impact of leaving it as is? I realise the only way to fix it will be to rebuild the ZPool, and as I have around 12TB of data on there that's not really an option.
3) Even if I did decide to rebuild the ZPool, how would I ensure that it wouldn't create 512 byte sector size again, given that it shouldn't be able to do this anyway?
Investigating my second question is what led me to the discovery of the above issue. FreeNAS is reporting 8 currently unreadable sectors on one of its drives (/dev/ada7). But I've run through a long SMART test (smartctl -t long /dev/ada7) and it shows zero errors. So now what do I do? Pull the drive and manually secure erase it?
Thanks for your help,
Trevor