@njj: I'm not so sure. According to a post from hmh just a few minutes ago on the above posted Crucial forum thread, the MX100 is not blacklisted in the kernel. Also, when I run "fstrim -v /", I get a response that bytes were trimmed. When I run it again, I get 0 bytes trimmed (see #53). Is this expected behaviour for a trim-disabled SSD?
-- 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
