Re: [OpenIndiana-discuss] Need Help Fixing Zpool misconfiguration
And the icing on the cake is the fact that in the newest OI (Osnet 17649 2018.10) you can't accidently do it anymore. Unfortunately in OI (Osnet 17625 2018.04) there was no -f required to add the singleton device. Well we will probably build a new Pool... Thanks for the answer. Looking forward for then new device_removal updates once they land Till On 11/22/18 06:41 PM, Guenther Alka wrote: > Only Solaris can remove a basic vdev from a pool with a raid-Z. Open-ZFS > cannot (yet) . If you cannot destroy/ recreate the pool you can only add > a disk to the basic vdev to make it a mirror (add redundancy) > > Gea > > > Am 22.11.2018 um 18:06 schrieb Till Wegmüller: >> Hello >> >> I had a slight mishap while configuring a Zpool. >> >> I wanted to re-add a spare disk again after we had replaced it and made >> a typo. Adding the device instead as top-level vdev. >> >> aka typed: >> zpool add $POOL $DEVICE >> instead of >> zpool add $POOL spare $DEVICE >> >> Turns out even with top-level device_removal feature turned on I cannot >> fix that typo. >> >> If I type >> zpool remove $POOL $DEVICE >> I get >> cannot remove $DEVICE: invalid config; all top-level vdevs must have the >> same sector size and not be raidz. >> >> Which is true because the rest of the Pool is part of a raidz2. >> >> And of course as murphy wants it I cannot just ditch that pool beacause >> it is too big to fit that data anywhere. >> >> While I would love for zpool remove to be able to remove the DEVICE in >> the future I wanted to ask you guys If you know a good Idea on how to >> Workaround that problem in the meantime. >> >> I really dont like having this single point of failure in the pool. >> >> Any advice would be greatly appreciated >> Thanks and Greetings >> Till >> >> ___ >> openindiana-discuss mailing list >> openindiana-discuss@openindiana.org >> https://openindiana.org/mailman/listinfo/openindiana-discuss > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Need Help Fixing Zpool misconfiguration
Huh odd Reading the Blog post associated with the Delphix device_removal feature that limitation does not make that much sense, since it is a straight up copy on a lov level block wise. Why would a different type of device make that approach not working. Greetings Till On 11/22/18 06:41 PM, Guenther Alka wrote: > Only Solaris can remove a basic vdev from a pool with a raid-Z. Open-ZFS > cannot (yet) . If you cannot destroy/ recreate the pool you can only add > a disk to the basic vdev to make it a mirror (add redundancy) > > Gea > > > Am 22.11.2018 um 18:06 schrieb Till Wegmüller: >> Hello >> >> I had a slight mishap while configuring a Zpool. >> >> I wanted to re-add a spare disk again after we had replaced it and made >> a typo. Adding the device instead as top-level vdev. >> >> aka typed: >> zpool add $POOL $DEVICE >> instead of >> zpool add $POOL spare $DEVICE >> >> Turns out even with top-level device_removal feature turned on I cannot >> fix that typo. >> >> If I type >> zpool remove $POOL $DEVICE >> I get >> cannot remove $DEVICE: invalid config; all top-level vdevs must have the >> same sector size and not be raidz. >> >> Which is true because the rest of the Pool is part of a raidz2. >> >> And of course as murphy wants it I cannot just ditch that pool beacause >> it is too big to fit that data anywhere. >> >> While I would love for zpool remove to be able to remove the DEVICE in >> the future I wanted to ask you guys If you know a good Idea on how to >> Workaround that problem in the meantime. >> >> I really dont like having this single point of failure in the pool. >> >> Any advice would be greatly appreciated >> Thanks and Greetings >> Till >> >> ___ >> openindiana-discuss mailing list >> openindiana-discuss@openindiana.org >> https://openindiana.org/mailman/listinfo/openindiana-discuss > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Need Help Fixing Zpool misconfiguration
Only Solaris can remove a basic vdev from a pool with a raid-Z. Open-ZFS cannot (yet) . If you cannot destroy/ recreate the pool you can only add a disk to the basic vdev to make it a mirror (add redundancy) Gea Am 22.11.2018 um 18:06 schrieb Till Wegmüller: Hello I had a slight mishap while configuring a Zpool. I wanted to re-add a spare disk again after we had replaced it and made a typo. Adding the device instead as top-level vdev. aka typed: zpool add $POOL $DEVICE instead of zpool add $POOL spare $DEVICE Turns out even with top-level device_removal feature turned on I cannot fix that typo. If I type zpool remove $POOL $DEVICE I get cannot remove $DEVICE: invalid config; all top-level vdevs must have the same sector size and not be raidz. Which is true because the rest of the Pool is part of a raidz2. And of course as murphy wants it I cannot just ditch that pool beacause it is too big to fit that data anywhere. While I would love for zpool remove to be able to remove the DEVICE in the future I wanted to ask you guys If you know a good Idea on how to Workaround that problem in the meantime. I really dont like having this single point of failure in the pool. Any advice would be greatly appreciated Thanks and Greetings Till ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Need Help Fixing Zpool misconfiguration
Hello I had a slight mishap while configuring a Zpool. I wanted to re-add a spare disk again after we had replaced it and made a typo. Adding the device instead as top-level vdev. aka typed: zpool add $POOL $DEVICE instead of zpool add $POOL spare $DEVICE Turns out even with top-level device_removal feature turned on I cannot fix that typo. If I type zpool remove $POOL $DEVICE I get cannot remove $DEVICE: invalid config; all top-level vdevs must have the same sector size and not be raidz. Which is true because the rest of the Pool is part of a raidz2. And of course as murphy wants it I cannot just ditch that pool beacause it is too big to fit that data anywhere. While I would love for zpool remove to be able to remove the DEVICE in the future I wanted to ask you guys If you know a good Idea on how to Workaround that problem in the meantime. I really dont like having this single point of failure in the pool. Any advice would be greatly appreciated Thanks and Greetings Till ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
