[LU-11993] lustre-rsync-test test_2c: remove from target yields rc=-2

• Status: Open
• Project: Lustre
• Affects Version/s: Lustre 2.12.1, Lustre 2.14.0
• Type: Bug
• Priority: Minor
• Reporter: Maloo
• Assignee: WC Triage
• Resolution: Unresolved
• Labels: dne, zfs
• Severity: 3

Description

This issue was created by maloo for Nathaniel Clark <[e-mail]>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/f7fd52b8-1a2c-11e9-a2cc-52540065bddc

test_2c failed with the following error:

Failure in replication; differences found.

Multiple occurences of unlink failing on targets:

***** Start 2057 UNLNK (6) [0x2000088d1:0x1ca:0x0] [0x2000088d1:0x113:0x0] RESULTS.XLS *****
remove: /tmp/target/.lustrerepl/[0x2000088d1:0x1ca:0x0]; rc=-2, errno=2
remove: /tmp/target/d2c.lustre-rsync-test/clients/client1/~dmtmp/EXCEL/RESULTS.XLS; rc1=-2, errno=2
remove: /tmp/target2/.lustrerepl/[0x2000088d1:0x1ca:0x0]; rc=-2, errno=2
remove: /tmp/target2/d2c.lustre-rsync-test/clients/client1/~dmtmp/EXCEL/RESULTS.XLS; rc1=-2, errno=2
##### End 2057 UNLNK (6) [0x2000088d1:0x1ca:0x0] [0x2000088d1:0x113:0x0] RESULTS.XLS rc=-2 #####

Might this be a DCO issue?

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
lustre-rsync-test test_2c - Failure in replication; differences found.

Comments

[Andreas Dilger]

+1 on master https://testing.whamcloud.com/test_sets/50757dfa-cb38-11e9-97d5-52540065bddc along with 13 others in the past 4 weeks.

[Li Xi]

Another similar but not the same one:

Error: 'Failure in replication; differences found.'

https://testing.whamcloud.com/test_sets/50757dfa-cb38-11e9-97d5-52540065bddc

[Li Xi]

Is there any real usage of lustre_rsync anywhere by anybody? If not, I am wondering whether removing the tool is proper. That would save a lot of maintaining effort for sure.

If we look for recent tickets related to lustre_rsync. Most of them (LU-11479 LU-11233 LU-10989 LU-10978 LU-10508 LU-10515) are test failures and compilation failures, zero actually usage problem. That implies we spend a lot of effort to maintain it without any benefit.

One value of lustre_rsync is using it as a test case of Changelog. But we could use the same effort to improve Changelog specific test codes and that would be more efficient.

[Artem Blagodarenko (Inactive)]

It looks like this happened again

https://testing.whamcloud.com/test_sets/8ed1d74a-6e16-4ac2-928f-d636f5f4a49e

[Chris Horn]

+1 on master https://testing.whamcloud.com/test_sets/047c442e-171d-42c1-8f44-196618efbf45