k3s/longhorn: use LVM to support additional storage disks #693
Conversation
This is a really simple use of LVM to just create a linear logical volume over `/dev/vd[b-z]`, then mount that for use by Longhorn. The default is still to deploy with only one additional disk, but at least now if more than one disk is requested, we'll actually do something with the extra disks. Signed-off-by: Tim Serong <tserong@suse.com>
|
Hang on, just tried a deploy on Tumbleweed which failed for some reason... |
Huh? |
|
Deployed again, didn't have the problem >sigh< I assume this is something potentially glitchy at some lower level than sesdev, so removing DNM label. |
|
Thinking about this further, I actually wonder if I should make this LVM setup optional, or perhaps just not bother doing it at all. My reason for adding longhorn support to sesdev in the first place was so I'd have a convenient playground for experimenting with longhorn. If I stitch all the extra disks together with LVM automatically, that means I can't play with Longhorn's "add disk" functionality... |
| mkfs.ext4 /dev/vdb | ||
|
|
||
| # This won't handle more than 25 disks. Tim is pretty sure that's fine. | ||
| vgcreate longhorn /dev/vd[b-z] |
There was a problem hiding this comment.
I probably shouldn't call the vg longhorn, because that means we end up with /dev/longhorn/longhorn-data, and /dev/longhorn is the namespace used for longhorn volumes.
This is a really simple use of LVM to just create a linear logical volume over
/dev/vd[b-z], then mount that for use by Longhorn. The default is still to deploy with only one additional disk, but at least now if more than one disk is requested, we'll actually do something with the extra disks.