On Sat, Jan 3, 2015 at 11:16 AM, Lutz Euler <lutz.euler@xxxxxxxxxx> wrote: > Martin Steigerwald wrote: > >> I have a 3.19-rc2 with a patch and a working fstrim now: > [...] >> I leave it to the patch author to come up with it on the mailing list :) > > That would be me. I have just sent in the patch; please see > http://www.mail-archive.com/linux-btrfs@xxxxxxxxxxxxxxx/msg40618.html > > For a discussion about the issue that goes into more detail than the > commit message and the code comments please see this thread: > http://comments.gmane.org/gmane.comp.file-systems.btrfs/15597 > At that time I had sent in a first version of this patch but it has not > been applied so far. I made the new version as the old one did not apply > any more since about kernel 3.9., and had a flaw (range->minlen was > being ignored). > > I am using this patch on my system since two years without problems with > kernel versions ranging from 3.3 to 3.16. > > Looking forward to a review, > Did this go anywhere? I don't see this in 3.18.13 unless I'm missing it, and I also have been unable to fstrim my ssd btrfs volume for as long as I've had it on an SSD. -- Rich -- 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
