Note that there are reports on the Crucial forum that the Crucial M550 has the same problem, and therefore because it uses the same controller (and firmware?), the MX100 does too:
http://forum.crucial.com/t5/Solid-State-Drives-SSD/M500-M5x0-QUEUED- TRIM-data-corruption-alert-mostly-for-Linux/m-p/154146#M43579 I'm not so brave any more, so I've removed the --no-model-check to the "exec fstrim-all" line in the cron fstrim file for my MX100. -- 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
