Hide Forgot
Created attachment 828512 [details] Full test log Description of problem: === full diff out/out.bad === --- /dev/fd/63 2013-11-15 09:09:29.031472181 -0500 +++ results/xfs/301.out.bad 2013-11-15 09:09:26.928586537 -0500 @@ -34,8 +34,6 @@ dir_text Attribute "attr1" had a 9 byte value for DUMP_DIR/smalll: some_text -Attribute "attrname" had a 4 byte value for DUMP_DIR/sparsefile: -1234 Attribute "attr3" had a 10 byte value for DUMP_DIR/sub/smalll: some_text3 Root names @@ -43,4 +41,6 @@ some_text2 Attribute "attr4" had a 10 byte value for DUMP_DIR/sub/biggg: some_text4 -Files 301.ea1 and 301.ea2 are identical +6,7d5 +< Attribute "attrname" had a 4 byte value for DUMP_DIR/sparsefile: +< 1234 Version-Release number of selected component (if applicable): xfsdump-3.1.3-1.el7 How reproducible: always Steps to Reproduce: 1. check xfs/301 on xfs 2. 3. Actual results: test fails Expected results: test passes Additional info:
Fixed upstream as well, same series - this might be a dup of 1034014 but need to remember which commit fixed which bug.
Fixed & built in xfsdump-3.1.3-2.el7
Verified with xfsdump-3.1.3-2.el7, xfs/301 passed Set to VERIFIED.
This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request.