From: Chandan Rajendra <chandan@linux.ibm.com>
To: Qian Cai <cai@lca.pw>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: xfs metadata corruption since 30 March
Date: Wed, 01 Apr 2020 09:44:01 +0530 [thread overview]
Message-ID: <11749734.KdfBBZeIvc@localhost.localdomain> (raw)
In-Reply-To: <990EDC4E-1A4E-4AC3-84D9-078ACF5EB9CC@lca.pw>
On Wednesday, April 1, 2020 3:27 AM Qian Cai wrote:
> Ever since two days ago, linux-next starts to trigger xfs metadata corruption
> during compilation workloads on both powerpc and arm64,
Can you please provide the filesystem geometry information?
You can get that by executing "xfs_info <mount-point>" command.
--
chandan
next prev parent reply other threads:[~2020-04-01 4:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 21:57 linux-next: xfs metadata corruption since 30 March Qian Cai
2020-03-31 22:13 ` Dave Chinner
2020-04-01 2:13 ` Qian Cai
2020-04-01 4:14 ` Chandan Rajendra [this message]
2020-04-01 4:15 ` Qian Cai
2020-04-01 4:45 ` Darrick J. Wong
2020-04-01 6:10 ` Chandan Rajendra
2020-04-01 13:54 ` Qian Cai
2020-04-01 12:34 ` Brian Foster
2020-04-01 16:21 ` Brian Foster
2020-04-01 18:24 ` Qian Cai
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=11749734.KdfBBZeIvc@localhost.localdomain \
--to=chandan@linux.ibm.com \
--cc=cai@lca.pw \
--cc=darrick.wong@oracle.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.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.