Comment # 1 on bug 1226043 from Luis Henriques

This seems to point at an issue with e2fsck, which reports a successful check:

> ROOT: clean, 65957/323840 files, 1043456/1306624 blocks

but it then fails mounting.

I guess you may have tried this already but it's worth asking: have you tried
to manually rerun e2fsck against that file system?  Did it still a similar
output (e.g. that it cleaned inode 18323, 48587, etc...)?

(There's a newer upstream release of the e2fsprogs that seem to have a few
fixes that seem related to orphan list processing, but unfortunately it's not
on TW yet.)