| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: new fs, xfs_admin new label, metadata corruption detected |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Tue, 15 Mar 2016 19:34:42 -0500 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CAJCQCtR4tq8+BXRX+Y4rkqn6ZrFLw-9SX=gXKkF3QS1b2c8Ksg@xxxxxxxxxxxxxx> |
| References: | <CAJCQCtR4tq8+BXRX+Y4rkqn6ZrFLw-9SX=gXKkF3QS1b2c8Ksg@xxxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 |
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
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | new fs, xfs_admin new label, metadata corruption detected, Chris Murphy |
|---|---|
| Next by Date: | Re: [PATCH v18 00/22] Richacls (Core and Ext4), Steve French |
| Previous by Thread: | new fs, xfs_admin new label, metadata corruption detected, Chris Murphy |
| Next by Thread: | Re: new fs, xfs_admin new label, metadata corruption detected, Chris Murphy |
| Indexes: | [Date] [Thread] [Top] [All Lists] |