https://bugzilla.redhat.com/show_bug.cgi?id=1479433
--- Comment #10 from Chris Murphy <bugzilla(a)colorremedies.com> ---
Well we need more information or it's all just speculation. There's plenty of
unallocated space, and no snapshots. There are no kernel complaints about the
file system in these logs, so if these logs don't show the problem we need
other logs. If you can boot single user mode, and at least get networking and
sshd running then you could remote in and 'journalctl f' to capture anything
that happens while transitioning to multi-user.target. At the moment there's
just nothing to go on.
The alternative is to reproduce in a VM backed by LVM LV, or if it must be a
file on Btrfs make sure to set chattr +C on the backing file at creation time
e.g. touch, then chattr, then fallocate -l). And now when booting the VM use
parameter console=ttyS0, and virsh console to record the failing boot process.
--
You are receiving this mail because:
You are on the CC list for the bug.