[GH-ISSUE #22] Drive replacement #20

Closed
opened 2026-05-05 03:29:31 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @Tualua on GitHub (Mar 16, 2019).
Original GitHub issue: https://github.com/ewwhite/zfs-ha/issues/22

Hi!
I have a question.
When I create stonith device with pcs stonith create fence-vol1 I use SCSI-address, e,g, 35000c500236032f7
What will happen when I need to replace faulty drive? Will SCSI address be the same or I will need to change stonith device?

Thanks!

Originally created by @Tualua on GitHub (Mar 16, 2019). Original GitHub issue: https://github.com/ewwhite/zfs-ha/issues/22 Hi! I have a question. When I create stonith device with **pcs stonith create fence-vol1** I use SCSI-address, e,g, _35000c500236032f7_ What will happen when I need to replace faulty drive? Will SCSI address be the same or I will need to change stonith device? Thanks!
Author
Owner

@ewwhite commented on GitHub (Mar 20, 2019):

Good question.

For the fencing to continue working, you will need to update the stonith to reflect the new drive's WWN and remove the old drive's WWN.

This can be done in the web GUI or by using a pcs stonith update command.

For example:
pcs stonith update fence-vol1 fence_scsi pcmk_monitor_action="metadata" devices="/dev/mapper/35000c5005612a19b,/dev/mapper/35000c500560e98cb,/dev/mapper/35000cca01c49e3e0,/dev/mapper/35000c50055f463ef,/dev/mapper/35000c5005612d27f,/dev/mapper/35000c5005612dbd3,/dev/mapper/35000c50055f4d54f,/dev/mapper/35000c5005608023f,/dev/mapper/35000c50055f4c593,/dev/mapper/35000c50055f4d2c7,/dev/mapper/35000c500561126bb,/dev/mapper/35000a7203008dd91" meta provides=unfencing"

<!-- gh-comment-id:474677275 --> @ewwhite commented on GitHub (Mar 20, 2019): Good question. For the fencing to continue working, you will need to update the stonith to reflect the new drive's WWN and remove the old drive's WWN. This can be done in the web GUI or by using a `pcs stonith update` command. For example: `pcs stonith update fence-vol1 fence_scsi pcmk_monitor_action="metadata" devices="/dev/mapper/35000c5005612a19b,/dev/mapper/35000c500560e98cb,/dev/mapper/35000cca01c49e3e0,/dev/mapper/35000c50055f463ef,/dev/mapper/35000c5005612d27f,/dev/mapper/35000c5005612dbd3,/dev/mapper/35000c50055f4d54f,/dev/mapper/35000c5005608023f,/dev/mapper/35000c50055f4c593,/dev/mapper/35000c50055f4d2c7,/dev/mapper/35000c500561126bb,/dev/mapper/35000a7203008dd91" meta provides=unfencing"`
Author
Owner

@Tualua commented on GitHub (Mar 21, 2019):

Thanks!

<!-- gh-comment-id:475187262 --> @Tualua commented on GitHub (Mar 21, 2019): Thanks!
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/zfs-ha#20
No description provided.