On Wed, Jul 18, 2012 at 11:34:32PM +0200, Clemens Eisserer wrote: > Hi, > > > Not using TRIM on my Crucial RealSSD C300 256GB is most likely what caused > > its garbage collection algorithm to fail (killing the drive and all its > > data), and it was also causing BRTFS to hang badly when I was getting > > within 10GB of the drive getting full. > > Funny thing, as without TRIM the drive does not even know how "full" it is ;) That's very true. To be honest, I don't fully know what happened to that drive, but I actually heard the following from Crucial tech support twice: "without TRIM, the drive needs to do garbage collection (correct), and it only happens when the drive has been fully idle for about 15mn (oh boy, why?). We recommend you let your drive sit at the bios or just with sata power from time to time so that it can do garbage collection" Then, there is also this gem: http://forums.crucial.com/t5/Solid-State-Drives-SSD/Bios-is-not-recognize-crucail-m4-SSD-64GB/td-p/63835 If the drive cannot garbage collect, it will shut off and appear dead. When that happens, it needs to be powered on for 20mn with no data, turned off, and on again for 20mn, and off. Then, it's supposed to come back and be usable again. (well, mine not so much. It came back eventually, but empty). This is not a btrfs problem per se, but since we had a discussion on TRIM and SSDs and what to do with dm-crypt, I thought I'd report back since it's actually not a simple situation at all, and very SSD dependent afterall. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
