All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 216486] [xfstests generic/447] xfs_scrub always complains  fs corruption
Date: Wed, 14 Sep 2022 17:59:14 +0000	[thread overview]
Message-ID: <bug-216486-201763-qMo1UjG1zL@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216486-201763@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216486

--- Comment #2 from Zorro Lang (zlang@redhat.com) ---
(In reply to Darrick J. Wong from comment #1)
> On Wed, Sep 14, 2022 at 08:12:56AM +0000, bugzilla-daemon@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=216486
> > 
> >             Bug ID: 216486
> >            Summary: [xfstests generic/447] xfs_scrub always complains  fs
> >                     corruption
> >            Product: File System
> >            Version: 2.5
> >     Kernel Version: 6.0.0-rc4+
> >           Hardware: All
> >                 OS: Linux
> >               Tree: Mainline
> >             Status: NEW
> >           Severity: normal
> >           Priority: P1
> >          Component: XFS
> >           Assignee: filesystem_xfs@kernel-bugs.kernel.org
> >           Reporter: zlang@redhat.com
> >         Regression: No
> > 
> > Recently xfstests generic/447 always fails[1][2][3] on latest xfs kernel
> with
> > xfsprogs. It's reproducible on 1k blocksize and rmapbt enabled XFS (-b
> > size=1024 -m rmapbt=1). Not sure if it's a kernel bug or a xfsprogs issue,
> or
> > an expected failure.
> 
> It's an expected failure that is one of the many things fixed by the
> online fsck patchset.  The solution I came up with is described here:
> https://djwong.org/docs/xfs-online-fsck-design/#eventual-consistency-vs-
> online-fsck
> 
> The TLDR is that scrub is probably racing with a thread that's in the
> middle of doing a file mapping change that involves both an rmap and a
> refcount update.  This is possible because we don't hold the AGF buffer
> between work items in a defer ops chain.

Thanks Darrick, for your reply and confirmation!

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2022-09-14 17:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14  8:12 [Bug 216486] New: [xfstests generic/447] xfs_scrub always complains fs corruption bugzilla-daemon
2022-09-14 17:45 ` Darrick J. Wong
2022-09-14 17:45 ` [Bug 216486] " bugzilla-daemon
2022-09-14 17:59 ` bugzilla-daemon [this message]

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=bug-216486-201763-qMo1UjG1zL@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-xfs@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.