From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: new fs, xfs_admin new label, metadata corruption detected
Date: Tue, 15 Mar 2016 19:34:42 -0500 [thread overview]
Message-ID: <56E8AA22.7080301@sandeen.net> (raw)
In-Reply-To: <CAJCQCtR4tq8+BXRX+Y4rkqn6ZrFLw-9SX=gXKkF3QS1b2c8Ksg@mail.gmail.com>
On 3/15/16 6:08 PM, Chris Murphy wrote:
> Is this expected? File system continues to work OK, sha256sum on the
> single file on this fs matches the source, but the metadata corruption
> messages are a bit scary so figured I'd ask about it.
>
> Filesystem created with
> xfsprogs-4.3.0-1.fc23
> kernel-4.4.4-300.fc23.x86_64
>
> mkfs.xfs defaults used on an LVM thinly provisioned volume on a single
> spinning disk.
>
> # xfs_info /dev/mapper/VG-testxfs
> meta-data=/dev/mapper/VG-testxfs isize=512 agcount=23, agsize=399984 blks
^^^^^^^^^^
It seems that you left a growfs step out of it, where does that come in
to the testcase?
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-03-16 0:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 23:08 new fs, xfs_admin new label, metadata corruption detected Chris Murphy
2016-03-16 0:34 ` Eric Sandeen [this message]
2016-03-16 7:23 ` Chris Murphy
2016-03-17 2:39 ` Chris Murphy
2016-03-17 2:40 ` Chris Murphy
2016-03-17 2:55 ` Chris Murphy
2016-03-17 6:39 ` Chris Murphy
2016-03-17 7:32 ` Zorro Lang
2016-03-17 20:57 ` Dave Chinner
2016-03-17 21:56 ` Dave Chinner
2016-03-17 23:21 ` Chris Murphy
2016-03-18 2:22 ` Dave Chinner
2016-03-18 4:43 ` Zorro Lang
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=56E8AA22.7080301@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