Project

General

Profile

Actions

Bug #10005

closed

Cannot Fix pool misconfiguration because other top level device is raidz.

Added by Till Wegmüller almost 3 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
-
Start date:
2018-11-22
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:

Description

Hello

I had a slight mishap. Instead of typing
zpool add bkpool spare c18t0d0

I typed
zpool add bkpool c18t0d0

without the spare. So basicly added the device as top level vdev to the pool.
And it turns out I now cannot remove that device:
zpool remove bkpool c18t0d0
cannot remove c18t0d0: invalid config; all top-level vdevs must have the same sector size and not be raidz.

That is a problem on my part and I probybly am screwed now as this is a productive pool. And I have absolutely no chance of migrating to another pool anytime soon.

However I am of the opinion that the removal should be allowed to work given that the disk Is only single and not raidz itself and there is no section in zpool-features(5) mentioning that problem.


Related issues

Related to illumos gate - Bug #10012: vioblk should not accept an all-zero serial numberClosedJoshua M. Clulow2018-11-28

Actions
Related to illumos gate - Feature #11329: improved Virtio frameworkClosedJoshua M. Clulow

Actions
Actions

Also available in: Atom PDF