From: "Richard W.M. Jones" <rjones@redhat.com>
To: xfs@oss.sgi.com
Subject: xfs_growfs causing "Metadata corruption detected at xfs_agf_read_verify"
Date: Thu, 17 Mar 2016 22:48:03 +0000 [thread overview]
Message-ID: <20160317224803.GA8856@redhat.com> (raw)
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.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-03-17 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 22:48 Richard W.M. Jones [this message]
2016-03-17 22:55 ` xfs_growfs causing "Metadata corruption detected at xfs_agf_read_verify" Eric Sandeen
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=20160317224803.GA8856@redhat.com \
--to=rjones@redhat.com \
--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 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.