Ok, this one is quite easy. The fsck fails, and because it opened the block device for writing, udev tells mountall to try it again - spawning fsck
We shouldn't spawn fsck or mount while mnt->error is set, and the plymouth keys function should clear the error before running with fix -- Infinite-loops in fsck when booting with damaged / https://bugs.launchpad.net/bugs/501801 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
