Am Thu, 13 Aug 2015 17:14:36 -0600 schrieb Chris Murphy <li...@colorremedies.com>:
> On Thu, Aug 13, 2015 at 3:23 AM, Marc Joliet <mar...@gmx.de> wrote: > > > Speaking as a user, since "fstrim -av" still always outputs 0 bytes trimmed > > on my system: what's the status of this? Did anybody ever file a bug > > report? > > Since I'm not having this problem with my SSD, I'm not in a position > to provide any meaningful information for such a report. > > The bug should whether this problem is reproducible with ext4 and XFS > on the same device, and the complete details of the stacking (if this > is not the full device or partition of it; e.g. if LVM, md, or > encryption is between fs and physical device). And also the bug should > include full dmesg as attachment, and strace of the fstrim command > that results in 0 bytes trimmed. And probably separate bugs for each > make/model of SSD, with the bug including make/model and firmware > version. > > Right now I think there's no status because a.) no bug report and b.) > not enough information. I was mainly asking because apparently there *is* a patch that helps some people affected by this, but nobody ever commented on it. Perhaps there's a reason for that, but I found it curious. (I see now that it was submitted in early January, in the thread "[PATCH V2] Btrfs: really fix trim 0 bytes after a device delete".) I can open a bug (I mean, that's part of being a user of btrfs at this stage), I'm just surprised that nobody else has. BTW, is there a way to tell if the "discard" mount option does anything? I'm curious about whether it could behave differently. -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup
pgp3RKB19fH0i.pgp
Description: Digitale Signatur von OpenPGP
