From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 201577] [xfstests generic/070]: XFS corruption and Oops when setxattr on 64k blocksize XFS
Date: Wed, 31 Oct 2018 22:42:54 +0000 [thread overview]
Message-ID: <bug-201577-201763-k2wEXF0DfO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201577-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201577
--- Comment #1 from Dave Chinner (david@fromorbit.com) ---
On Wed, Oct 31, 2018 at 07:34:49AM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=201577
>
> Bug ID: 201577
> Summary: [xfstests generic/070]: XFS corruption and Oops when
> setxattr on 64k blocksize XFS
......
> How reproducible:
> nearly 100% on 64k blocksize XFS on ppc64le
>
> Additional info:
> Can't reproduce this bug on 4k blocksize XFS
I saw both these (the corruption and the assert on shutdown) a few
days ago on a 4k block size filesystem. Not reproducable, though,
but it doesn't have anything specifically to do with 64k block size.
What kernel are you running, exactly? A plain 4.19 release kernel?
Cheers,
Dave.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-11-01 7:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 7:34 [Bug 201577] New: [xfstests generic/070]: XFS corruption and Oops when setxattr on 64k blocksize XFS bugzilla-daemon
2018-10-31 22:42 ` Dave Chinner
2018-10-31 22:42 ` bugzilla-daemon [this message]
2018-11-01 1:40 ` [Bug 201577] " bugzilla-daemon
2018-12-07 17:07 ` bugzilla-daemon
2020-06-10 3:38 ` bugzilla-daemon
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-201577-201763-k2wEXF0DfO@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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.