Following-up my previous comment:  While dracut-core initially seemed to
fix the corruption problem, I did eventually get some small corruption
again (which BTRFS immediately detected), and it turns out that at some
point I had started getting some (smaller) shutdown errors again (I
don't know why):

systemd-shutdown[1]: Could not detach DM /dm/dm-3: Device or resource busy
systemd-shutdown[1]: Could not detach DM /dm/dm-0: Device or resource busy
systemd-shutdown[1]: Failed to finalize DM devices, ignoring.

As I'd since bought & switched to a new NVMe drive, which is large
enough to completely contain my cached / and /home partitions, I
disabled lvmcache, and switched to LVM -type raid1 --mirrors 1 instead
(with --raidwritemostly used to avoid reading from my slow spinning disk
of rust).  This appears to have completely solved my shutdown errors,
but I have not yet tried disabling dracut-core to see if that's still
needed.  (I suspect that performance is also better, since everything is
cached immediately, rather than having to be read one or more times
first.)

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

Title:
  systemd-shutdown cannot detach DM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/finalrd/+bug/1905166/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to