I collected the log in comment 23 and 24 yesterday, and then walked away. Looked at the console from that system today, and it shows: [54550.928492] EXT4-fs error (device dm-9): htree_dirblock_to_tree:914: inode #7078166: block 28319821: comm updatedb.mlocat: bad entry in directory: directory entry across range - offset=0(0), inode=0, rec_len=98572, name_len=74
So it seems that even though I successfully booted, there are some errors, they just weren't found in boot. It is somewhat arbitrary failure, so you might seem OK or might not get through the first boot (as mike has shown). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1462530 Title: multipath errors on vivid and wily kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462530/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
