From: Roman Mamedov <rm@romanrm.net>
To: Forza <forza@tnonline.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: FSTRIM timeout/errors on WD RED SA500 NAS SSD
Date: Fri, 24 Jun 2022 23:37:22 +0500 [thread overview]
Message-ID: <20220624233722.05038e48@nvm> (raw)
In-Reply-To: <98c43f5e-2091-b222-edad-632caef9f9e3@tnonline.net>
On Fri, 24 Jun 2022 17:23:27 +0200
Forza <forza@tnonline.net> wrote:
> Can we work around the Btrfs fstrim issue, for example by splitting up
> fstrim requests in "discard_max_bytes" sized chunks?
If I'm not mistaken, those discard_max_* are honoured automatically by a lower
level than the submitting filesystem (i.e. the block layer).
It seems like the linux-ide list (or is it linux-scsi for SAS?) could be better
suited to hunt down this issue. Especially if aside from Btrfs even just a
simple blkdiscard also shows trouble.
Btw, did you try lowering discard_max_bytes in sysfs, and then retrying
blkdiscard?
--
With respect,
Roman
next prev parent reply other threads:[~2022-06-24 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 15:23 FSTRIM timeout/errors on WD RED SA500 NAS SSD Forza
2022-06-24 18:37 ` Roman Mamedov [this message]
2022-06-24 22:45 ` Forza
2022-06-24 22:55 ` Roman Mamedov
2022-06-25 6:44 ` Qu Wenruo
2022-06-25 10:34 ` Forza
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=20220624233722.05038e48@nvm \
--to=rm@romanrm.net \
--cc=forza@tnonline.net \
--cc=linux-btrfs@vger.kernel.org \
/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