[Bug 1696102] Comment bridged from LTC Bugzilla

[bugproxy]

------- Comment From hasriram at in.ibm.com 2017-09-22 13:12 EDT-------
(In reply to comment #21)
> Accepted xfsprogs into zesty-proposed. The package will build now and be
> available at
> https://launchpad.net/ubuntu/+source/xfsprogs/4.3.0+nmu1ubuntu4.1 in a few
> hours, and then in the -proposed repository.

The issue is resolved on zesty

xfs/073	 12s
Ran: xfs/073
Passed all 1 tests

# dpkg -l | grep xfsp
ii  xfsprogs                                      4.3.0+nmu1ubuntu4.1                      ppc64el      Utilities for managing the XFS filesystem

> Accepted xfsprogs into xenial-proposed. The package will build now and be
> available at
> https://launchpad.net/ubuntu/+source/xfsprogs/4.3.0+nmu1ubuntu1.1 in a few
> hours, and then in the -proposed repository.
>

The issue is resolved on xenial

xfs/073	 15s
Ran: xfs/073
Passed all 1 tests

# dpkg -l | grep xfsp
ii  xfsprogs                             4.3.0+nmu1ubuntu1.1                        ppc64el      Utilities for managing the XFS filesystem

Thanks,
Harish

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to xfsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1696102

Title:
  xfs/073 test fails with Metadata corruption detected on xfs file
  system (xfsprogs)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in xfsprogs package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in xfsprogs source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Invalid
Status in xfsprogs source package in Zesty:
  Fix Committed

Bug description:
  Impact
  ======
  When making multiple copies of a V5 filesystem with xfs_copy those copies will be corrupt due to incorrect UUIDs.

  Test Case
  =========
  See the detailed steps to create the test environment in comment #20.

  Regression Potential
  ====================
  From the patch "Most of this patch is changing comments and re-ordering tests to match; the functional change is to simply use the *sb rather than the *ag_hdr to identify the proper metadata UUID." So this seems pretty straightforward and given that copy process is currently broken, because the copies are corrupt, this will be an improvement.

  Original Description
  ====================

  Problem Description
  --------------------------------
  xfs/073 test fails with Metadata corruption detected on xfs file system. Test fails with _check_xfs_filesystem: filesystem on /mnt/test/84004.image2 is inconsistent.

  # diff -u tests/xfs/073.out /root/xfstests-dev/results//xfs/073.out.bad
  --- tests/xfs/073.out	2017-03-23 12:13:05.288877197 +0530
  +++ /root/xfstests-dev/results//xfs/073.out.bad	2017-03-27 11:11:43.023059702 +0530
  @@ -59,8 +59,7 @@
   comparing new image geometry to old
   unmounting and removing new image
   checking new image
  -mounting new image on loopback
  -comparing new image files to old
  -comparing new image directories to old
  -comparing new image geometry to old
  -unmounting and removing new image
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent (c)
  +(see /root/xfstests-dev/results//xfs/073.full for details)
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent (r)
  +(see /root/xfstests-dev/results//xfs/073.full for details)

  Metadata corruption detected at xfs_agf block 0x1/0x200

  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  ----------------------------------------
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd xfstests-dev
  3. make
  4. Create a local.conf for running with created loop device
  5.. Run xfstests-dev test  : ./check tests/xfs/073

  Full log is attached.

  == Comment: #2 - Harish Sriram <hasriram at in.ibm.com> - 2017-05-31 01:22:11 ==
  (In reply to comment #1)
  > Hi Harish,
  > Can you share the steps used in creating the loop device with xfs filesystem
  > ?
  >
  > Thank you.

  Create loop device:
  # mkdir /mnt/loop-device /mnt/test /mnt/scratch

  # for i in $(seq 0 1); do fallocate -o 0 -l 5GiB /mnt/loop-device/file-$i.img; done
  # for i in $(seq 0 1); do losetup /dev/loop$i /mnt/loop-device/file-$i.img; done

  Create File system:
  # for i in $(seq 0 1); do mkfs.ext4 -F /dev/loop$i; done

  # cat local.config
  export TEST_DEV=/dev/loop0
  export TEST_DIR=/mnt/test
  export SCRATCH_DEV=/dev/loop1
  export SCRATCH_MNT=/mnt/scratch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696102/+subscriptions