SCALE drive replacement within a pool produces drive busy error
Description
Problem/Justification
Impact
relates to
Activity
Automation for Jira November 22, 2022 at 2:35 PM
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 November 22, 2022 at 2:33 PM
Closing this ticket as https://github.com/truenas/zfs/pull/105#pullrequestreview-1190132506 is merged to truenas 2.1 release branch. There is another related PR https://github.com/openzfs/zfs/pull/14181, that is not yet merged but it should not affect the 22.12 release as pools in SCALE are created with autoexpand property that works around the issue. Created https://ixsystems.atlassian.net/browse/NAS-119106 to track the related PR.
Ameer Hamza November 15, 2022 at 4:16 PM
@Michelle Johnson Nevermind, I see it in the Linked issues.
Ameer Hamza November 15, 2022 at 4:13 PM
@Michael Johnson Just to let you know, we already have a ticket for this https://ixsystems.atlassian.net/browse/NAS-118739, which is under review.
Automation for Jira November 15, 2022 at 4:10 PM
Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.
https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153
Details
Details
Assignee
Reporter
Labels
Fix versions
Affects versions
Priority
MediumMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
TrueNAS-SCALE-22.12-MASTER-20221026-081046
Testing Seagate IronWolf 8TB/18TB drives for qualification purposes. Created a mirrored pool to test drive replacement within said pool. Pulled a drive and inserted same family of drive in its place. Worked without issue for 2 cycles. 3rd try resulted in the following error:
Error: [EFAULT] Failed to wipe disk sdb: [Errno 16] Device or resource busy: '/dev/sdb'
For clarification I test with 3 drives when conducting qualifications. So when I replace a drive in this manner within a pool, I am using the same 2 drives in a rotating manner utilizing the FORCE option when replacing a drive that was previously utilized within a pool after the first cycle of testing.