Remove busted metadata SSD

[itractus]

Got it. So
1: attach drives to mirror metadata devices.
2: Move everything at once? (how would i go about this?)

 

[asap2go]

Isn't it possible to send the data on the striped metadata vdev onto a newly created mirror and replace the striped vdev with some config fiddleing?
I thought something similar could be done when upgrading a single drive boot pool to a mirror.

 

[Etorix]

You cannot remove any data vdev (including metadata!) if the pool contains a raidz# member. Two striped special vdevs there are; two striped special vdevs shall remain. The best one can do is to make these striped vdevs redundant.

 

[Etorix]

2: Move everything at once? (how would i go about this?)

Buy enough drives to store your 39 TB with a safe and sane pool layout… (Yes, I know your wallet will NOT like that, but ZFS is an enterprise-class product and solves problems the enterprise-class way: By throwing money at them!)

 

[itractus]

There is no way to kick the metadata device out at all?

 

[Patrick M. Hausen]

Since your pool contains RAIDZ vdevs - no. Only from pools built exclusively from mirror vdevs can data vdevs be removed.

 

[itractus]

And phyisically removing the devices will lose all pool data.... right?

 

[Patrick M. Hausen]

Correctamundo.

 

[itractus]

welp. To the hard disk store it is then :D

 

[Etorix]

And physically removing the devices will lose all pool data.... right?

This sad story was about a dedup vdev, but special vdev would be exactly the same:

I lost my Dedup VDev Disk and Pool UNAVAIL

I added an Optane SSD for Dedup VDev some days ago and tested dedup performance, but it seems not very good. Then I try to delete the SSD from zpool and use it for other things, but failed. So I shut down the TrueNAS host and unplugged the SSD then erased it for other systems. When I turn on...

www.truenas.com

 

[itractus]

life lessons right there. Luckily all my important data is backed up offsite. This is mainly linux ISO's