summaryrefslogtreecommitdiff
path: root/src/initrd/grok-block
diff options
context:
space:
mode:
authorAndrew Cady <d@cryptonomic.net>2021-03-02 17:36:19 -0500
committerAndrew Cady <d@cryptonomic.net>2021-03-02 18:17:24 -0500
commit60f81e1cd5b9c7f4c3249f1f6e6f2d62d70e6e11 (patch)
tree19f69e0adbac88eac973f123bcacd7fc8d8af255 /src/initrd/grok-block
parent3619754c55abae45b3c41200d0c511485843a9ac (diff)
Fix to make the btrfs install method work.
Just figured this out. We must change the fsuid after removing the devices, because btrfs MODIFIES the READ-ONLY SEED DEVICES to mark them unavailable after when remove them from the read-write device. When we reboot with the UNMODIFIED, IMMUTABLE seed image, btrfs cannot handle the duplicate fsuid. We detect this situation (kind of) and call btrfstune -m to change the fsuid of the /dev/mapper/samizdatcrypt single device fs. Now it just works. It would be much better to call this on the booted system on the running rootfs, but btrfs can't, so we instead call it on the initrd mount time. A more proper fix might use the partition table to mark the partition as in need of 'btrfstune -m'.
Diffstat (limited to 'src/initrd/grok-block')
0 files changed, 0 insertions, 0 deletions