curtin-dev team mailing list archive

[Ryan Harper <1884161@xxxxxxxxxxxxxxxxxx>]

** Also affects: curtin
   Importance: Undecided
       Status: New

** Changed in: curtin
       Status: New => In Progress

-- 
You received this bug notification because you are a member of curtin
developers, which is subscribed to curtin.
https://bugs.launchpad.net/bugs/1884161

Title:
  swap file unsuitable for btrfs

Status in curtin:
  In Progress
Status in subiquity:
  New

Bug description:
  There is a corresponding ubiquity bug: 
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818811

  To summarize, installing Ubuntu 20.04 LTS to a btrfs filesystem causes
  systemd to report a degraded system.  Installation proceeds without
  error, but the swap file fails to activate.

  In general, swap files need to be carefully configured on btrfs.  The
  requirements, as far as I know:

  1. linux kernel >5
  2. single device btrfs volume
  3. copy-on-write disabled on the swap file
  4. compression disabled on the swap file
  5. no snapshots of the subvolume containing the swap file

  On a clean install of Ubuntu 20.04 LTS, I believe 1, 4, and 5 are
  guaranteed.  I think 2 is currently guaranteed because subiquity can't
  configure a multi-device btrfs volume, and Ubuntu doesn't by default
  boot from such a volume without some extra tweaking.  The main issue
  is 3.

  There is a fix of sorts described in the ubiquity bug, although permissions should also be fixed and the swap file also needs to be initialized: 
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818811/comments/7

  That fix is probably suitable for the way subiquity currently
  operates.  It might not be appropriate if subiquity allows more
  complicated btrfs configurations.  There's probably a conversation to
  be had at some point about btrfs support in general.

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1884161/+subscriptions