I have tried to use some metadata and log VDEVs but I turned out not to benefit from this configuration or at least I haven’t found a benefit worth that in my use case.
I would like to remove the drives used for those VDEVs but I have seen that it can cause data to be lost, I would like to be sure that I don’t do a mistake.
Is there a proper way to stop using a VDEV and remove them safely from my system ?
Did you create a checkpoint? If not, or your checkpoint is “too old”, then you’re left with removing the special vdev only if it is a mirror or stripe.
Otherwise, you’re stuck with it, unless you rebuild and repopulate a new pool.
Just remove the SLOG from GUI. No data loss.
Removing the special vdev, however, depends on what else is in the pool:
- Mirrors GOOD, just remove the vdev from GUI (data will be moved).
- Raidz BAD, you’re locked with the special vdev until the pool is destroyed.
3 Likes
@etorix, this is a forum for all types of end-users, some of whom do not have deep knowledge of software and tech. Please try to avoid using complex and technical words.
4 Likes
Let’s educate those unsavvy ones. iX's ZFS Pool Layout White Paper
2 Likes
What @etorix was saying (and saying explicitly in the original answer) was that the GOOD and BAD related to the ability to remove a metadata vDev.
This precis (for the purposes of comedy) leaves this open to reinterpretation that RAIDZ is generally a bad thing - which most here understand is not the case.
1 Like
Fortunately, the full original message is just above the partial citation.
First Rule of surviving the Disinformation Age: Always check sources.
Ah - you know that and I know that but many people (and also AIs and especially those people that blindly believe AIs) don’t know that.
1 Like
Asking AI instead of searching yourself is the plague of the next generation.
1 Like
Note that the above digression came from a reply by @winnielinnie —but he’s an AI, surely? 
2 Likes
Thank you for the informations.
1 Like