zed: unclean disk attachment faults the vdev
Description
Problem/Justification
None
Impact
None
relates to
Activity
Show:
Automation for Jira December 28, 2022 at 11:29 AM
This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.
Ameer Hamza December 28, 2022 at 11:28 AM
zfs 2.1.8 PR:
Ameer Hamza December 27, 2022 at 5:48 PM
It is merged upstream but not in our repo yet. It will be a part of zfs-2.1.8 release.
William Gryzbowski December 27, 2022 at 5:21 PM
was this already merged in our repo? Can you update the ticket, please?
Ameer Hamza November 22, 2022 at 2:36 PM
Upstream PR:
Complete
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Ameer HamzaReporter
Ameer HamzaLabels
Impact
Low
Fix versions
Priority
MediumMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Created November 22, 2022 at 2:29 PM
Updated February 6, 2023 at 7:25 PM
Resolved December 28, 2022 at 11:29 AM
If the attached disk already contains a vdev GUID, it means the disk is not clean. In such a scenario, the physical path would be a match that makes the disk faulted when trying to online it. So, we would only want to proceed if either GUID matches with the last attached disk or the disk is in a clean state.