mirror of
https://github.com/ewwhite/zfs-ha.git
synced 2026-05-15 14:16:09 -06:00
[GH-ISSUE #27] Storage fencing with full NVME based setup #27
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/zfs-ha#27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cu12 on GitHub (Apr 29, 2019).
Original GitHub issue: https://github.com/ewwhite/zfs-ha/issues/27
Hi all,
I can see you use
fence_scsihere, although I couldn't find any equivalent to do the same with NVME. Actually, I found that there's no fencing agent for NVME :/ https://bugzilla.redhat.com/show_bug.cgi?id=1700165Any ideas for this?
I have a two VMs setup with physical disks presented to them for ZFS.
@ewwhite commented on GitHub (Jun 15, 2019):
I'm not sure what the design of your solution is. Can you describe it in better detail?
@cu12 commented on GitHub (Jun 17, 2019):
Hi @ewwhite I'm planning two create a simple two node setup, but instead of having scsi or ssd disks, mine are all nvme disks, where fence_scsi (or scsi equivalent translation methods) doesn't apply. Hope this made it a bit more clearer :)
@ewwhite commented on GitHub (Jun 17, 2019):
How do you expect this to work?
@efschu commented on GitHub (Jun 18, 2019):
For fencing I'm using fence_ipmilan, described here
https://github.com/efschu/AP-HA-CIAB-ISER/wiki
btw thanks @ewwhite for your guide, without yours mine would never have get written ;)