From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Sebastian Ochmann <ochmann@cs.uni-bonn.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Filesystem mounts fine but hangs on access
Date: Tue, 6 Nov 2018 08:38:40 +0200 [thread overview]
Message-ID: <d6c607f3-8def-bc8e-756a-487ba43a6202@suse.com> (raw)
In-Reply-To: <41f9e8ca-d5f9-4d2b-caf0-a810096dbfc3@gmx.com>
On 5.11.18 г. 2:23 ч., Qu Wenruo wrote:
> Great, then it's completely free space cache causing the problem.
>
> You could use -o nospace_cache mount option to avoid the problem as a
> workaround.
>
> Free space cache only speed up free extent search, it doesn't has extra
> effect on the fs (except the bug).
> So you could disable free space cache without problem.
I'd rather recommend him use -o space_cache=v2
next prev parent reply other threads:[~2018-11-06 6:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 13:15 Filesystem mounts fine but hangs on access Sebastian Ochmann
2018-11-04 13:37 ` Qu Wenruo
2018-11-04 17:00 ` Sebastian Ochmann
2018-11-05 0:23 ` Qu Wenruo
2018-11-06 6:38 ` Nikolay Borisov [this message]
2018-11-04 18:29 ` Duncan
2018-11-04 19:55 ` Adam Borowski
2018-11-05 0:29 ` Duncan
[not found] <20181104113137.3ca6043e@ws>
2018-11-04 19:18 ` Sebastian Ochmann
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=d6c607f3-8def-bc8e-756a-487ba43a6202@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=ochmann@cs.uni-bonn.de \
--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