@Jeffrey, I don't know for sure, but I'd say it's likely that two drives from the same manufacturer using the same controller will at the very least be both derived from the same firmware code base, and their firmware will therefore likely have a lot of bugs (and features) in common. Since your drive is from another manufacturer (or is it just a relabelled Crucial drive?), it's maybe more likely to have significantly different firmware, and maybe less likely to have the corruption bug. My bet would be the corruption problem is a firmware problem, one that could be fixed. If it is indeed a silicon problem, it could be worked around in the firmware, or features could be disabled to ensure data integrity.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
