github-starred/zfs-ha
2
0
Fork 0
mirror of https://github.com/ewwhite/zfs-ha.git synced 2026-05-15 14:16:09 -06:00
Code Issues 11 Projects Packages Wiki Activity Actions

[GH-ISSUE #2] GPT-label instead of multipath #2

New issue
Closed
opened 2026-05-05 03:28:07 -06:00 by gitea-mirror · 2 comments
gitea-mirror commented 2026-05-05 03:28:07 -06:00
Owner
Copy link

Originally created by @colttt on GitHub (Sep 7, 2016).
Original GitHub issue: https://github.com/ewwhite/zfs-ha/issues/2

Hello,

first, very very good howto!
But I would recommend to use GPT-Labels instead of multipath, because you hace 36characters to specify which disk in which enclosure it is, thats better to support if a disk failes.. for example: r1e12d7-SN1234567 = r=rack, e=enclosure, d=disk and the Serialnumber.. at first it is a little bit of work to get all these correct information, but if something fails it is good to act very fast.

best regards

Originally created by @colttt on GitHub (Sep 7, 2016). Original GitHub issue: https://github.com/ewwhite/zfs-ha/issues/2 Hello, first, very very good howto! But I would recommend to use GPT-Labels instead of multipath, because you hace 36characters to specify which disk in which enclosure it is, thats better to support if a disk failes.. for example: r1e12d7-SN1234567 = r=rack, e=enclosure, d=disk and the Serialnumber.. at first it is a little bit of work to get all these correct information, but if something fails it is good to act very fast. best regards
gitea-mirror commented 2026-05-05 03:28:10 -06:00
Author
Owner
Copy link

@ewwhite commented on GitHub (Sep 12, 2016):

The default is to use mpath or multipath/WWN devices. Drive location is going to be a function of your controller and enclosure setup, so there's no deterministic way to derive locations across the variety of potential configurations out there.

Are GPT labels acceptable as zpool creation devices?

<!-- gh-comment-id:246221196 --> @ewwhite commented on GitHub (Sep 12, 2016): The default is to use mpath or multipath/WWN devices. Drive location is going to be a function of your controller and enclosure setup, so there's no deterministic way to derive locations across the variety of potential configurations out there. Are GPT labels acceptable as zpool creation devices?
gitea-mirror commented 2026-05-05 03:28:12 -06:00
Author
Owner
Copy link

@colttt commented on GitHub (Sep 12, 2016):

Are GPT labels acceptable as zpool creation devices?
Yes, its the same what you find here: /dev/disk/by-partlabel/

I know that the raidcontroller/enclosure don't say me in which bay is which Harddisk, but i can find it out and then this informations are very usefull.. you can blink the LED harddrives to find it out..

<!-- gh-comment-id:246356888 --> @colttt commented on GitHub (Sep 12, 2016): > Are GPT labels acceptable as zpool creation devices? > Yes, its the same what you find here: /dev/disk/by-partlabel/ I know that the raidcontroller/enclosure don't say me in which bay is which Harddisk, but i can find it out and then this informations are very usefull.. you can blink the LED harddrives to find it out..
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
pull-request

Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#2
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?