From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Sebastian Ochmann <ochmann@cs.uni-bonn.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Filesystem mounts fine but hangs on access
Date: Mon, 5 Nov 2018 08:23:53 +0800 [thread overview]
Message-ID: <41f9e8ca-d5f9-4d2b-caf0-a810096dbfc3@gmx.com> (raw)
In-Reply-To: <d493b9d8-2ed6-4dfa-d546-e9a09c5924a6@cs.uni-bonn.de>
[-- Attachment #1.1: Type: text/plain, Size: 2402 bytes --]
On 2018/11/5 上午1:00, Sebastian Ochmann wrote:
> Thank you very much for the quick reply.
>
> On 04.11.18 14:37, Qu Wenruo wrote:
>>
>>
>> On 2018/11/4 下午9:15, Sebastian Ochmann wrote:
>>> Hello,
>>>
>>> I have a btrfs filesystem on a single encrypted (LUKS) 10 TB drive which
>>> stopped working correctly. The drive is used as a backup drive with zstd
>>> compression to which I regularly rsync and make daily snapshots. After I
>>> routinely removed a bunch of snapshots (about 20), I noticed later that
>>> the machine would hang when trying to unmount the filesystem. The
>>> current state is that I'm able to mount the filesystem without errors
>>> and I can view (ls) files in the root level, but trying to view contents
>>> of directories contained therein hangs just like when trying to unmount
>>> the filesystem. I have not yet tried to run check, repair, etc. Do you
>>> have any advice what I should try next?
>>
>> Could you please run "btrfs check" on the umounted fs?
>
> I ran btrfs check on the unmounted fs and it reported no errors.
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.
Thanks,
Qu
>
[snip]
>> This looks pretty like this bug which should be fixed by the following
>> patch:
>>
>> https://patchwork.kernel.org/patch/10654433/
>>
>> If previous "btrfs check" shows no error, would you please try apply
>> that patch and try again?
>
> I tried applying the patch to the 4.18.16 kernel I was running and it
> didn't apply cleanly, so I thought maybe I'd update to 4.19.0 first
> (which is already in the Arch testing repos) and then try applying the
> patch to that.
>
> However, as it turns out, the fs now works again just by using 4.19.0
> even though I think the patch is not even in 4.19 yet (?). I'm able to
> navigate the directories and unmounting also works fine. Even after
> downgrading to 4.18.16, the fs still works.
>
> So, thanks again for the quick reply, and "sorry" for not being able to
> test this particular patch now, but I guess the problem has been resolved.
>
>> Thanks,
>> Qu
>>
>
> Thanks,
> Ochi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-11-05 0:24 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 [this message]
2018-11-06 6:38 ` Nikolay Borisov
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=41f9e8ca-d5f9-4d2b-caf0-a810096dbfc3@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=ochmann@cs.uni-bonn.de \
/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