I'm not a dev, but I know that first error, and it's not what it seems.Wanted to benchmark the disk, but for some reason unable to remove it from dedup duties...
If dedup data is not volatile and necessary, why did it assign the disks in stripe and not mirror by default?
SAS 3.74T 52.1T 56 112 268K 2.74M
raidz2 3.73T 50.8T 40 51 204K 532K
gptid/50cad0f1-d0d7-11ea-8717-2cf05d07d39b - - 4 5 20.3K 53.2K
gptid/511b4e3f-d0d7-11ea-8717-2cf05d07d39b - - 4 5 20.4K 53.2K
gptid/51294ecd-d0d7-11ea-8717-2cf05d07d39b - - 4 5 20.2K 53.2K
gptid/517b5371-d0d7-11ea-8717-2cf05d07d39b - - 4 5 20.3K 53.2K
gptid/51907b32-d0d7-11ea-8717-2cf05d07d39b - - 4 5 20.3K 53.2K
gptid/51924d04-d0d7-11ea-8717-2cf05d07d39b - - 4 5 20.3K 53.3K
gptid/51a8084b-d0d7-11ea-8717-2cf05d07d39b - - 4 5 20.4K 53.2K
gptid/5189a1b0-d0d7-11ea-8717-2cf05d07d39b - - 4 5 20.4K 53.2K
gptid/51df64e8-d0d7-11ea-8717-2cf05d07d39b - - 4 5 20.3K 53.2K
gptid/51e871f0-d0d7-11ea-8717-2cf05d07d39b - - 4 5 20.5K 53.2K
dedup - - - - - -
gptid/85c84ce9-e23b-11ea-ba69-2cf05d07d39b 8.37G 436G 11 10 44.4K 520K
gptid/863904ee-e23b-11ea-ba69-2cf05d07d39b 3.18G 441G 4 3 17.7K 187K
special - - - - - -
mirror 2.42G 442G 0 10 2.54K 254K
gptid/ded6ac5d-e224-11ea-ba69-2cf05d07d39b - - 0 5 1.31K 127K
gptid/deea7ff4-e224-11ea-ba69-2cf05d07d39b - - 0 5 1.23K 127K
logs - - - - - -
mirror 123M 6.38G 0 39 13 1.35M
gptid/d73be473-e939-11ea-bd27-2cf05d07d39b - - 0 19 6 693K
gptid/d9886192-e939-11ea-bd27-2cf05d07d39b - - 0 19 6 693K
---------------------------------------------- ----- ----- ----- ----- ----- -----
---------------------------------------------- ----- ----- ----- ----- ----- -----
root@freenas[~]# gpart list da13 | egrep 'Mediasize|rawuuid'
Mediasize: 480113504256 (447G)
rawuuid: 863904ee-e23b-11ea-ba69-2cf05d07d39b
Mediasize: 480113590272 (447G)
root@freenas[~]#
View attachment 41152
View attachment 41153
View attachment 41154
View attachment 41155
This is an error generated by the "zpool remove" command. It's something that isn't mentioned in the man pages and while not a "bug", it's certainly an undescribed and quite problematic behaviour of the underlying removal process.
zpool remove states that the command can be used to clear and remove a top level vdev. When you try to run it in reality, it checks the vdev sector sizes across the entire pool, and requires them to have the same sector sizes, or it won't be able to execute the removal command. The vdevs must also be mirrors and not raidz.
I don't know why it needs those restrictions to move data, but they aren't in the man page, or warned about. More worryingly even if all top level vdevs are mirrors with the same sector size, I've had it still complain the same way (pool made 100% of 4096 logical/512 physical mirrorred disks).
As for why no valid replicas, that I'm less sure about. But this is the meaning of your "All top level vdevs must have the same sector size" message.
IMPROVEMENT/FIX REQUEST FOR THIS ISSUE: https://jira.ixsystems.com/browse/NAS-107397
(Feel free to comment as well)
Last edited: