From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: xfs_growfs causing "Metadata corruption detected at xfs_agf_read_verify"
Date: Thu, 17 Mar 2016 17:55:52 -0500 [thread overview]
Message-ID: <56EB35F8.1030601@sandeen.net> (raw)
In-Reply-To: <20160317224803.GA8856@redhat.com>
On 3/17/16 5:48 PM, Richard W.M. Jones wrote:
>
> With recent kernels (or maybe xfsprogs?) we've noticed strange
> filesystem corruption after using xfs_growfs.
>
> Examples:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1315895 (on aarch64)
> https://www.redhat.com/archives/libguestfs/2016-March/msg00113.html (x86_64)
> https://rwmj.wordpress.com/2015/11/04/virt-builder-fedora-23-image/#comment-15668 (x86_64)
>
> Do these errors look familiar? I don't yet have a simple test case,
> still working on that.
try:
http://oss.sgi.com/pipermail/xfs/2016-March/047683.html
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-03-17 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 22:48 xfs_growfs causing "Metadata corruption detected at xfs_agf_read_verify" Richard W.M. Jones
2016-03-17 22:55 ` Eric Sandeen [this message]
2016-03-18 12:31 ` Richard W.M. Jones
2016-03-20 21:58 ` Dave Chinner
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=56EB35F8.1030601@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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