From: "Hendrik Friedel" <hendrik@friedels.name>
To: "Chris Murphy" <lists@colorremedies.com>
Cc: "Chris Murphy" <lists@colorremedies.com>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re[4]: Filesystem sometimes Hangs
Date: Wed, 31 Mar 2021 14:03:58 +0000 [thread overview]
Message-ID: <emf567b17e-42d3-4c32-b254-a19d06ed87c5@desktop-g0r648m> (raw)
In-Reply-To: <CAJCQCtQH=k_h7CyRLysea0NgqadPnOVtVTGzdU9pG69RRhqL+g@mail.gmail.com>
Hello Chris,
thanks again for your reply.
>
>> 5.10.0-0.bpo.3-amd64
>
>It's probably OK. I'm not sure what upstream stable version this
>translates into, but current stable are 5.10.27 and 5.11.11. There
>have been multiple btrfs bug fixes since 5.10.0 was released.
>
>I missed in your first email this line:
Ok, I am compiling 5.11.11.
>>[Mo Mär 29 09:29:21 2021] BTRFS info (device sdc2): turning on sync discard
>
>Remove the discard mount option for this file system and see if that
>fixes the problem. Run it for a week or two, or until you're certain
>the problem is still happening (or certain it's gone). Some drives
>just can't handle sync discards, they become really slow and hang,
>just like you're reporting.
In fstab, this option is not set:
/dev/disk/by-label/DataPool1 /srv/dev-disk-by-label-DataPool1
btrfs noatime,defaults,nofail 0 2
How do I deactivate discard then?
These drives are spinning disks. I thought that discard is only relevant
for SSDs?
Regards,
Hendrik
>
>
next prev parent reply other threads:[~2021-03-31 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 11:11 Filesystem sometimes Hangs Hendrik Friedel
2021-03-29 18:07 ` Chris Murphy
2021-03-30 12:50 ` Re[2]: " Hendrik Friedel
2021-03-31 6:27 ` Chris Murphy
2021-03-31 14:03 ` Hendrik Friedel [this message]
2021-03-31 20:11 ` Re[4]: " Chris Murphy
2021-04-03 16:12 ` Re[6]: " Hendrik Friedel
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=emf567b17e-42d3-4c32-b254-a19d06ed87c5@desktop-g0r648m \
--to=hendrik@friedels.name \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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;
as well as URLs for NNTP newsgroup(s).