Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

storage: Improve handling of LUKS backed btrfs #20070

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Commits on Apr 5, 2024

  1. storage: Improve handling of LUKS backed btrfs

    Single-device btrfs volumes now behave like other filesystems:
    Unmounting all subvolumes will automatically lock the LUKS device, and
    mounting the first subvolume will automatically unlock it.
    
    Options in /etc/crypttab are now maintained correctly for btrfs
    volumes with multiple subvolumes. For example, the LUKS device is only
    "noauto" when all of the subvolumes are also "noauto", and it is
    readonly exactly when all of the subvolumes are readonly.
    
    Cockpit can't unfortunately always know whether a locked LUKS device
    is part of a single-device or multi-device btrfs volume.  (Because
    UDisks2 only tracks one parent of a fstab entry, we would need to fix
    that.) We assume that they are single-device volumes (because they are
    more common, probably) and let the user mount their subvolumes
    directly.
    
    If the assumption turns out to have been wrong, the mount operation is
    cleanly aborted.
    mvollmer committed Apr 5, 2024
    Configuration menu
    Copy the full SHA
    77ace98 View commit details
    Browse the repository at this point in the history