[Bug 1871244] [NEW] btrfs snapshot restore read-only

[Dark Dragon]

Public bug reported:

When trying to restore a btrfs snapshot, it is renamed as-is. When
snapshots are created read-only (which is good practice), then reboot
will fail for a read-only root file system.

I suggest to create a child read-write snapshot instead. This has the following advantages
- target snapshot is read-write
- source snapshot can be used multiple times in case something goes wrong

A snapshot can be created via:

  mv @ @apt-old-root-DATE
  btrfs subvolume snapshot $SNAPSHOT @

** Affects: friendly-recovery (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to friendly-recovery in Ubuntu.
https://bugs.launchpad.net/bugs/1871244

Title:
  btrfs snapshot restore read-only

Status in friendly-recovery package in Ubuntu:
  New

Bug description:
  When trying to restore a btrfs snapshot, it is renamed as-is. When
  snapshots are created read-only (which is good practice), then reboot
  will fail for a read-only root file system.

  I suggest to create a child read-write snapshot instead. This has the following advantages
  - target snapshot is read-write
  - source snapshot can be used multiple times in case something goes wrong

  A snapshot can be created via:

    mv @ @apt-old-root-DATE
    btrfs subvolume snapshot $SNAPSHOT @

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1871244/+subscriptions