Conversation
jarkko

Jarkko Sakkinen

WiP: Archest Linux (EXT4 + LUKS2 - LVM2): https://codeberg.org/jarkko/archest-linux/src/tag/0.1.0-rc1 Boots to login and only minor glitches still left to fixup before tagging 0.1 šŸ³

I like how unlayered this is, i.e. at most two subsystems layered and stack is at its heaviest a file system + LUKS2 volume (i.e. no one to many relationships). Less risk of busy file systems that cannot be unmounted at least :-)
1
0
1
mikebabcock@floss.social

Michael T Babcock

Reply to @jarkko

@jarkko I don't see why one would avoid LVM when using EXT4. The original post discusses btrfs not needing the volume management, but LVM + LUKS + EXT4/XFS is a fantastically stable system (I know, I use it on dozens of servers every day).

1
0
0
jarkko

Jarkko Sakkinen

Reply to @mikebabcock@floss.social
@mikebabcock Yep, breakin' the law I guess šŸ˜… But you know this WFM me best...
1
0
0
jarkko

Jarkko Sakkinen

Reply to @jarkko
@mikebabcock and had no other choice than arch as ext4 is not favoured with this oddball combination choice of modern and legacy features. I do e.g. use snapshots but for that I use incremental backups to my NAS rather than pile them all over the place šŸ¤·ā€ā™€ļøšŸ’£šŸ„²
1
0
0
jarkko

Jarkko Sakkinen

Reply to @jarkko
@mikebabcock Iā€™m going to use lvm2 after all. There is a useful commands depending on it: e2scrub. So it is a constraint then.
1
0
1
mikebabcock@floss.social

Michael T Babcock

Reply to @jarkko

@jarkko I primarily use LVM so I don't need to allocate all my disk space up front, and to give me access to LVM cache. I use xfs for my filesystems so I have xfsdump for consistent backups.

1
0
1
jarkko

Jarkko Sakkinen

Reply to @mikebabcock@floss.social
@mikebabcock I also realized that it makes sense to have swap as LVM2 volume because I have essentially two different swap configurations depending on use and purpose: 2GB (non-hibernate) and 60-80GB (hibenate). LVM2 will help in this case later on tune between these choices a bit...
1
0
0
jarkko

Jarkko Sakkinen

Reply to @jarkko
@mikebabcock I'm doing this partly to research what would be optimal configuration to enable hibernate, and possibly try out encrypted hibernate patch set, which never landed to the mainline. So I'm doing both reconfiguration for my host system and designing something for test target VM's at the same time :-)

One observation is that probably it is better to encrypt per logical volume than encrypt the physical volume because then the partition is reachable for so called restore kernel. I've previously encrypted the physical volume and created logical volumes inside it.
1
1
1
mikebabcock@floss.social

Michael T Babcock

Reply to @jarkko

@jarkko I don't like encrypting anything with too much well-known structure in case it becomes an attack vector, so I do the same; disk -> lvm -> luks -> xfs in my case. I tend to not encrypt root filesystems on servers for recovery reasons, and often use "real" partitions for /boot and swap, again to improve recovery options.

1
0
0
jarkko

Jarkko Sakkinen

Reply to @mikebabcock@floss.social
@mikebabcock i have zero plans to use hibernation in my hosts but i'm interested to test it as a kernel feature :-) and generally i want a common image that works for my host system and test targets (usually VM's ,sometimes NUC's).
0
0
1
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: