sunshine931
Explorer
- Joined
- Jan 23, 2018
- Messages
- 54
I'm looking to clarify what is likely a misunderstanding on my end.
To make a long story short, I have a pool that consists of many vdevs, all mirrors. I accidentally added a new mirror vdev to the pool and wish to remove that vdev from the pool.
I've read the zpool man page, and came across this:
This made me hopeful - I don't use raidz, I use mirrored pairs for my vdevs. So, I tried the following and am receiving an error:
I'm looking at this error and don't understand what it's trying to tell me. I cannot find instructions around how to determine a vdev sector size (wouldn't this be the device's sector size?), and my pool is not raidz (it's a collection of mirrored pair vdevs).
Looking at my physical devices, all the vdevs have drives (including the accidentally added vdev drives) with 512 byte sectors, as per "diskinfo -v".
I'm guessing I'm missing something in my understanding of what this means. Can someone clarify please?
Thanks!
To make a long story short, I have a pool that consists of many vdevs, all mirrors. I accidentally added a new mirror vdev to the pool and wish to remove that vdev from the pool.
I've read the zpool man page, and came across this:
Code:
zpool remove [-np] pool device ... Removes the specified device from the pool. This command currently only supports removing hot spares, cache, log devices and mirrored top-level vdevs (mirror of leaf devices); but not raidz. Removing a top-level vdev reduces the total amount of space in the storage pool. The specified device will be evacuated by copying all allocated space from it to the other devices in the pool. In this case, the zpool remove command initiates the removal and returns, while the evacuation continues in the background. The removal progress can be monitored with zpool status. This feature must be enabled to be used, see zpool-features(5) A mirrored top-level device (log or data) can be removed by specifying the top-level mirror for the same. Non-log devices or data devices that are part of a mirrored configuration can be removed using the "zpool detach" command. -n Do not actually perform the removal ("no-op"). Instead, print the estimated amount of memory that will be used by the mapping table after the removal completes. This is nonzero only for top-level vdevs. -p Used in conjunction with the -n flag, displays numbers as parsable (exact) values.
This made me hopeful - I don't use raidz, I use mirrored pairs for my vdevs. So, I tried the following and am receiving an error:
Code:
[root@omega ~]# zpool remove nebula mirror-8 cannot remove mirror-8: invalid config; all top-level vdevs must have the same sector size and not be raidz. [root@omega ~]#
I'm looking at this error and don't understand what it's trying to tell me. I cannot find instructions around how to determine a vdev sector size (wouldn't this be the device's sector size?), and my pool is not raidz (it's a collection of mirrored pair vdevs).
Looking at my physical devices, all the vdevs have drives (including the accidentally added vdev drives) with 512 byte sectors, as per "diskinfo -v".
I'm guessing I'm missing something in my understanding of what this means. Can someone clarify please?
Thanks!