mirror of
https://github.com/ewwhite/zfs-ha.git
synced 2026-05-15 22:05:04 -06:00
[GH-ISSUE #21] SLOG and L2ARC setup not described #21
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#21
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 @severgun on GitHub (Jan 17, 2019).
Original GitHub issue: https://github.com/ewwhite/zfs-ha/issues/21
You describe hardware, but there is no description how to set them.
BOOM!
cache spares logs
what? where? how?
Could it be added later? Should it be shared or hostbased?
@ewwhite commented on GitHub (Jan 17, 2019):
Spares are just pool drives.
Cache can be shared (SAS) or independent (one per host).
Logs need to be shared SAS disks.
I can look into updating this...
@severgun commented on GitHub (Jan 17, 2019):
I understand this from other isssue here.
I mean there is no instructions how to set them up. Just result.
Also. What about using vdev_id.conf aliases? Is it acceptable?
@ewwhite commented on GitHub (Jan 17, 2019):
What do you need help with?
@severgun commented on GitHub (Jan 17, 2019):
Is it acceptable to use /dev/disk/by-vdev/*** names to create HA pool and in pcs?
/dev/disk/by-vdev/*** names generated based on vdev_id.conf
https://github.com/zfsonlinux/zfs/wiki/FAQ#selecting-dev-names-when-creating-a-pool
As I understand conf should be same on both head nodes.
@ewwhite commented on GitHub (Apr 3, 2019):
I'd recommend /dev/mapper multipath devices for zpool creation.