15.04.2016 05:27, Chris Murphy пишет:

I've managed to successfully blow up Btrfs in a Tumbleweed VM. And root fs is not mounting at boot time. What I have is:

"A start job is running for Remount Root and Kernel File Systems (5min 22s / no limit)"

I added 'rd.shell' as a boot parameter but this hasn't changed this. Is there a good reason why there's no limit for root fs remount? Seems like there should be some limit. 3 minutes? 10 minutes?

If this were baremetal, I'd want to get to an rdsosreport or grab the journal. For now I can probably get this with rd.break=pre-mount or maybe virsh console will get me the call trace.

This happens after switch to real root, so dracut debug logs are probably not helpful here. You could try to launch systemd debug terminal which at least gives you early shell to poke around. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

15.04.2016 05:27, Chris Murphy пишет:

I've managed to successfully blow up Btrfs in a Tumbleweed VM. And root fs is not mounting at boot time. What I have is:

"A start job is running for Remount Root and Kernel File Systems (5min 22s / no limit)"

I added 'rd.shell' as a boot parameter but this hasn't changed this. Is there a good reason why there's no limit for root fs remount? Seems like there should be some limit. 3 minutes? 10 minutes?

If this were baremetal, I'd want to get to an rdsosreport or grab the journal. For now I can probably get this with rd.break=pre-mount or maybe virsh console will get me the call trace.

This happens after switch to real root, so dracut debug logs are probably not helpful here. You could try to launch systemd debug terminal which at least gives you early shell to poke around. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org