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: Sat, 25 Jun 2022 03:55:43 +0500 [thread overview]
Message-ID: <20220625035543.2c65c834@nvm> (raw)
In-Reply-To: <fae6e07f-6ad3-218c-f220-c8b159d5ec3c@tnonline.net>
On Sat, 25 Jun 2022 00:45:55 +0200
Forza <forza@tnonline.net> wrote:
> I have tried lowering the discard_max_bytes, but it did not help - on
> the contrary it takes much longer to do the blkdiscard /dev/sdf and does
> not solve the problem.
Should be possible to verify exactly which size discard requests are being
submitted to the device, using https://linux.die.net/man/8/blktrace
In no event requests larger than discard_max_bytes should be seen.
If lowering it does not help, perhaps after a sustained stream of those,
some individual requests, even small, start to take longer than 30s?
> However, since btrfs-progs do split discard ranges into smaller chunks,
> and that ext4 seems to handle this as well, I think it is worth looking
> into handling.
That's not something to be handled on the FS side, even if one of them
happens to work, by luck. I suggest to focus on diagnosing with blkdiscard
only, and proceed to FSes only after that has been made to work reliably.
--
With respect,
Roman
next prev parent reply other threads:[~2022-06-24 22:55 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
2022-06-24 22:45 ` Forza
2022-06-24 22:55 ` Roman Mamedov [this message]
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=20220625035543.2c65c834@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.