On Tue, Mar 15, 2016, 6:34 PM Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
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="" 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?
Much of this happened in Cockpit, which uses storaged. So no matter what I'll have to backtrack to get exact reproduce steps. In the meantime:
Create thin pool
Create thin volume
Mkfs
Mount
Copy file
Grow (resize done in cockpit)
Delete file
Umount
Kernel and progs update and reboot
Mount
Copy file
Unmount
Relabel
<error>
Repair
Mount
Something amiss with growfs and lvresize steps?
Chris Murphy
_______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
