Comment 2 for bug 498390

Boot most probably fails because the ext3 filesystem becomes corrupted when it fills up, I could reproduce it on two different computers, with two different sticks.

The writable overlay is implemented as an LVM snapshot which lives in a separate file. My guess is that the snapshot runs out of empty pages and then starts reporting errors to the filesystem layer. To avoid further data loss, ext3 will refuse to mount if there are uncommitted entries in the journal that can't be replayed.

All the relevant error messages are being suppressed by the quiet boot and we only end up seeing a spurious "tried to remove a fb that we didn't own", which is just a red herring.

I propose that we upstream this bug to the Fedora folks.