Only allow addition of vdevs of the same type to a pool
Description
Problem/Justification
Impact
relates to
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
Dru Lavigne October 17, 2019 at 5:58 PM
Docs verified in new UI version of Guide.
Aaron St. John [X] September 25, 2019 at 3:33 PM
(docs) angulargui PR: https://github.com/freenas/freenas-docs/pull/1559
Erin Clark September 12, 2019 at 1:15 AM
Master PR: https://github.com/freenas/webui/pull/2745
This should prevent users from creating vdevs that don't have enough disks in them
Aaron St. John [X] September 11, 2019 at 7:09 PM
(QE) Test fails Version: FreeNAS-11.3-MASTER-201909111119
Test case:
1. Create a pool with RAIDz1 vdev type.
2. Go to Storage>Pools>Extend. (No error message is displayed. This part passes)
3. Select one disk and try to extend the existing RAIDz1 vdev.
4. Observe that the EXTEND button is clickable, and a warning is displayed as well as a dialog warning displayed.
5. Follow through with extending and observe the error (screenshot and code posted below).
Erin Clark September 3, 2019 at 10:45 PM
Master PR: https://github.com/freenas/webui/pull/2709
Details
Details
Assignee
Erin ClarkReporter
Arwen EvenstarLabels
Components
Fix versions
Priority
Low
More fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Users sometimes ignore / not understand any warning that their pool mixes RAID-Zx & single disk vDevs. Then, when it blows up, they ask for help. If we could get them warned, with perhaps a web link to straight forward information on why this is bad, then perhaps we can reduce future problems.
Technically this same issue can apply to Mirrored pools that have a single disk that is un-mirrored. But, at least that may be temporary until a replacement or new disk is made available.
My thought is to have this warning E-Mailed to them with the normal FreeNAS status. Both to a web link, and instructions on how to disable this warning, for this pool, in case they understand the risks.
Since this would be in the first E-Mail after creation, or addition of single disk vDev, they would hopefully still have the change they made in mind.
Note that I would add logic to the warning, such that a pool with zero vDev redundancy, would NOT be warned. Such pools have their uses, and are generally created that way on purpose. (Like a R/O media server... where the actual master copies are elsewhere.)