Project

General

Profile

Bug #2185

Danger of accidentally adding their ZIL or L2ARC to Zpool as a member disk

Added by jake - over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Important
Assignee:
-
Category:
GUI (new)
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

When using the [[FreeNAS]] web GUI to add a ZIL, or an L2ARC to an existing zpool there is a danger of adding this device as a member disk of a vdev.
For instance after selecting volume to extend. One can identically select the zil as a member disk rather than a log device or cache device in zfs extra.

The GUI should validate that a user hasn't selected a device for both a pool disk and an extra function (cache, log, or spare) and show an error if attempted. There's multiple possible implementations of this constraint.
We need something done to keep people from permanently breaking their pools while trying to perform a regular maintenance operation.

History

#1 Updated by William Grzybowski over 6 years ago

  • Status changed from Unscreened to Closed

I believe this has already been addressed in 9.x with a new volume manager.

Also available in: Atom PDF