• Illecors@lemmy.cafe
    link
    fedilink
    English
    arrow-up
    21
    ·
    8 months ago

    That… Is literally how you do it. You install the system onto a subvolume. Or many, in fact - the way I do. Root, var, srv, home, opt all get their own subvolume. Only boot stays as a separate partition.

    • fruitcantfly@programming.dev
      link
      fedilink
      arrow-up
      8
      ·
      8 months ago

      Ignoring /boot, what is the benefit of putting everything else in different subvolumes? As opposed to just one subvolume for / and one for /home, which is what I currently have. It just looks to me like it’d be extra work, but I’m probably missing something

      • SteveTech@aussie.zone
        link
        fedilink
        arrow-up
        15
        ·
        8 months ago

        You can snapshot them independently. E.g. I snapshot / on every update and boot, /home every boot, and temporary file directories such as /tmp & /var/tmp don’t get snapshot at all and are also mounted with nodev,nosuid,noexec flags.

      • infiniteface@programming.dev
        link
        fedilink
        arrow-up
        4
        ·
        8 months ago

        For one thing if you’re snapshotting your subvolumes for backup purposes then it will ignore nested subvolumes. Eg you dont want to preserve snapshots of huge installed game directories, cache directories, logs or docker / podman images, usually. Saves a lot of space.

        Also you can tune copy on write on a subvolume, which is great for some use cases for performance.