On Sun, Sep 27, 2015 at 10:45 PM, Duncan <1i5t5.dun...@cox.net> wrote: > But I think part of reasoning behind the relatively low priority this > issue has received is that it's a low visibility issue not really > affecting most people running btrfs, either because they're not running > on ssd or because they simply don't have a particularly high awareness of > what trim does and thus about how it's failing to work here and what that > means to them. If we get a rash of people posting on-list that it's > affecting them, that relative priority is likely to go up, and with it > the patch testing and integration schedule for the affected patches.
I've never actually seen fstrim do anything on btrfs (0 bytes trimmed). I stopped using it a few months ago when the news came out about all the issues with its implementation, and I believe my drive is still blacklisted anyway. It really should be fixed, but right now that goes all around - if btrfs fixed it tomorrow I'd still be stuck until somebody figures out how to reliably do it on a Samsung 850. -- Rich -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
