From: Roman Mamedov <rm@romanrm.net>
To: "Massimo B." <massimo.b@gmx.net>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: I/O blocked after booting
Date: Thu, 28 Mar 2024 22:24:26 +0500 [thread overview]
Message-ID: <20240328222426.6cd2c31d@nvm> (raw)
In-Reply-To: <94addf02f0eac5e5f402f48f41d16cb80d17470b.camel@gmx.net>
On Thu, 28 Mar 2024 15:55:15 +0100
"Massimo B." <massimo.b@gmx.net> wrote:
> What can I do about that failed to trim?
> I have tried this on different disks like
>
> Samsung SSD 970 EVO Plus 1TB NVMe
> and
> Samsung SSD 860 EVO 1TB SATA
>
> Trying again after the failed to trim, I got it finished again with
> 156,8 GiB (168413265920 bytes) trimmed
>
> Should fstrim be fast if it was just finished some minutes before? Why there are
> again more than 100GiB to be trimmed shortly after the last run?
>
> Is there anything broken with the trim on these devices?
860 EVO do have a bad history with TRIM and NCQ on some controllers:
https://bugzilla.kernel.org/show_bug.cgi?id=203475
But IIRC the affected combinations should have a fix in the kernel by now.
970 is not known to be affected.
Most importantly, do you see any ata errors in dmesg? Such as "SEND FPDMA
QUEUED", or any other.
--
With respect,
Roman
next prev parent reply other threads:[~2024-03-28 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 13:13 I/O blocked after booting Massimo B.
2024-03-28 8:36 ` HAN Yuwei
2024-03-28 10:10 ` Qu Wenruo
2024-03-28 10:39 ` Massimo B.
2024-03-28 14:55 ` Massimo B.
2024-03-28 17:24 ` Roman Mamedov [this message]
2024-03-28 20:23 ` Qu Wenruo
2024-06-14 8:32 ` Massimo B.
2024-06-14 21:57 ` Qu Wenruo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240328222426.6cd2c31d@nvm \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=massimo.b@gmx.net \
--cc=quwenruo.btrfs@gmx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox