[Kernel-packages] [Bug 1259829] Re: 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

2014-04-18 Thread Fabien Lusseau
I tested on a KINGSTON v300 and a v100 and everything works fine. I used the discard mount option as it seems to be the most efficient to detect this misbehavior. And then I started: sudo apt-get build-dep libreoffice; apt-get source -b libreoffice It worked fine, I also tried with periodic

[Kernel-packages] [Bug 1259829] Re: 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

2014-04-02 Thread Fabien Lusseau
What kind of heavy simple test can I run on my Kingston and Kingspec SSDs to know if they also are affected by this kind of problems ? A simple testing method should help build the whitelist/blacklist. I have access to several SSDs from a lot of manufacturers, the only ones that are not already