linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wang Yugui <wangyugui@e16-tech.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: fdmanana@gmail.com, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: 'ls /mnt/scratch/' freeze(deadlock?) when run xfstest(btrfs/232)
Date: Thu, 22 Apr 2021 08:32:32 +0800	[thread overview]
Message-ID: <20210422083231.755B.409509F4@e16-tech.com> (raw)
In-Reply-To: <e8886729-6f82-eca9-d752-0e81145794fe@gmx.com>

Hi,

> >>> we run xfstest on two server with this patch.
> >>> one passed the tests.
> >>> but one got a btrfs/232 error.
> >>>
> >>> btrfs/232 32s ... _check_btrfs_filesystem: filesystem on
> >>> /dev/nvme0n1p1is inconsistent
> >>> (see /usr/hpc-bio/xfstests/results//btrfs/232.full for details)
> >>> ...
> >>> [4/7] checking fs roots
> >>> root 5 inode 337 errors 400, nbytes wrong
> >>> ERROR: errors found in fs roots
> >>
> >> Ok, that's a different problem caused by something else.
> >> It's possible to be due to the recent refactorings for preparation to
> >> subpage block size.
> >
> > This error looks exactly what I have seen during subpage development.
> > The subpage bug is caused by incorrect btrfs_invalidatepage() though,
> > and not yet merged into misc-next anyway.
> >
> > I guess it's some error path not clearing extent states correctly, thus
> > leaving the inode nbytes accounting wrong.
> >
> > BTW, the new @in_reclaim_context parameter for start_delalloc_inodes()
> > is already in misc-next:
> > commit 3d45f221ce627d13e2e6ef3274f06750c84a6542
> > Author: Filipe Manana <fdmanana@suse.com>
> > Date:?? Wed Dec 2 11:55:58 2020 +0000
> >
> >  ?? btrfs: fix deadlock when cloning inline extent and low on free
> > metadata space
> >
> > We only need to make btrfs_start_delalloc_snapshot() to accept the new
> > parameter and pass in_reclaim_context = true for qgroup.
> 
> Strangely, on my subpage branch, with new @in_reclaim_context parameter
> added to btrfs_start_delalloc_snapshot(), I can't reproduce the nbytes
> mismatch error in 32 runs loop.
> I guess one of the refactor around ordered extents and invalidatepage
> may fix the problem by accident.
> 
> Mind to test my subpage branch
> (https://github.com/adam900710/linux/tree/subpage) with the attached diff?

The attached diff( more in_reclaim_context) seems a replacement for 
https://pastebin.com/raw/U9GUZiEf (less in_reclaim_context).

so I  will firstly test with the attached diff but drop
https://pastebin.com/raw/U9GUZiEf.

The test of whole subpage branch will be done later.

Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2021/04/22



  reply	other threads:[~2021-04-22  0:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21  0:31 'ls /mnt/scratch/' freeze(deadlock?) when run xfstest(btrfs/232) Wang Yugui
2021-04-21 12:17 ` Wang Yugui
2021-04-21 13:29   ` Filipe Manana
2021-04-21 15:57     ` Wang Yugui
2021-04-21 16:03       ` Filipe Manana
2021-04-21 23:19         ` Qu Wenruo
2021-04-21 23:43           ` Qu Wenruo
2021-04-22  0:32             ` Wang Yugui [this message]
2021-04-22  0:57               ` Qu Wenruo
2021-04-22  1:25                 ` Wang Yugui
2021-04-22  4:16                 ` Wang Yugui
2021-04-22 11:06                   ` Filipe Manana
2021-04-22 10:59           ` Filipe Manana

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=20210422083231.755B.409509F4@e16-tech.com \
    --to=wangyugui@e16-tech.com \
    --cc=fdmanana@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).