[LU-6644] lustre-rsync-test test_2b:fid2path error: (/mnt/lustre, [0x200000007:0x2:0x0]) 22 Invalid argument Created: 26/May/15  Updated: 06/Jun/16  Resolved: 06/Jun/16

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.9.0

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Related
is related to LU-4781 lustre-rsync-test test_2b: Replicatio... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for wangdi <di.wang@intel.com>

This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/1966f84a-024a-11e5-9144-5254006e85c2.

The sub-test test_2b failed with the following error:

test failed to respond and timed out

[0x200000007:0x2:0x0] is the FID for echo root, I do not know how it exists in lustre-rsync test. Let's if it is repeatable.

== lustre-rsync-test test 2b: Replicate files changed by dbench. == 07:12:16 (1432476736)
CMD: onyx-64-ib lctl --device lustre-MDT0000 changelog_register -n
lustre-MDT0000: Registered changelog user cl9
CMD: onyx-64-ib lctl get_param -n mdd.lustre-MDT0000.changelog_users
Other changelog users present (2)
waiting child_pid=$(pgrep dbench), 355 secs left ...
copying /usr/share/dbench/client.txt to /mnt/lustre/d2b.lustre-rsync-test/client.txt
copying necessary libs to /mnt/lustre/d2b.lustre-rsync-test
lib64/libpopt.so.0
lib64/libc.so.6
lib64/ld-linux-x86-64.so.2
running 'dbench 2 -t 60' in /mnt/lustre/d2b.lustre-rsync-test at Sun May 24 07:12:17 PDT 2015
dbench PID=45824
dbench version 4.00 - Copyright Andrew Tridgell 1999-2004

Running for 60 seconds with load 'client.txt' and minimum warmup 12 secs
0 of 2 processes prepared for launch   0 sec
2 of 2 processes prepared for launch   0 sec
releasing clients
   2       664    42.32 MB/sec  warmup   1 sec  latency 270.700 ms
   2       664    21.16 MB/sec  warmup   2 sec  latency 1270.972 ms
   2       666    14.11 MB/sec  warmup   3 sec  latency 1387.690 ms
   2       670    10.58 MB/sec  warmup   4 sec  latency 1193.759 ms
   2       674     8.47 MB/sec  warmup   5 sec  latency 960.536 ms
   2       699     7.08 MB/sec  warmup   6 sec  latency 930.463 ms
   2       723     6.08 MB/sec  warmup   7 sec  latency 1002.787 ms
   2       726     5.33 MB/sec  warmup   8 sec  latency 893.697 ms
   2       729     4.74 MB/sec  warmup   9 sec  latency 1032.026 ms
   2       758     4.28 MB/sec  warmup  10 sec  latency 896.875 ms
   2       760     3.89 MB/sec  warmup  11 sec  latency 1043.556 ms
   2       792     0.15 MB/sec  execute   1 sec  latency 933.205 ms
   2       794     0.08 MB/sec  execute   2 sec  latency 1037.028 ms
PIDs: 45824 45825 45826
Stopping dbench
Starting replication
ioctl err -22: Invalid argument (22)
fid2path error: (/mnt/lustre, [0x200000007:0x2:0x0]) 22 Invalid argument
ioctl err -22: Invalid argument (22)
fid2path error: (/mnt/lustre, [0x200000007:0x2:0x0]) 22 Invalid argument
Replication of operation failed(-22): 4291 RMDIR (7) [0x200002340:0x1:0x0] [0x200000007:0x2:0x0] MDT0000-tests
ioctl err -22: Invalid argument (22)
fid2path error: (/mnt/lustre, [0x200000007:0x2:0x0]) 22 Invalid argument
ioctl err -22: Invalid argument (22)
fid2path error: (/mnt/lustre, [0x200000007:0x2:0x0]) 22 Invalid argument
Replication of operation failed(-22): 4292 RMDIR (7) [0x200002341:0x1:0x0] [0x200000007:0x2:0x0] MDT0000-tests1
ioctl err -22: Invalid argument (22)
fid2path error: (/mnt/lustre, [0x200000007:0x2:0x0]) 22 Invalid argument
ioctl err -22: Invalid argument (22)
fid2path error: (/mnt/lustre, [0x200000007:0x2:0x0]) 22 Invalid argument
Replication of operation failed(-22): 7295 RMDIR (7) [0x200002346:0x1:0x0] [0x200000007:0x2:0x0] MDT0000-tests
ioctl err -22: Invalid argument (22)
fid2path error: (/mnt/lustre, [0x200000007:0x2:0x0]) 22 Invalid argument
ioctl err -22: Invalid argument (22)
fid2path error: (/mnt/lustre, [0x200000007:0x2:0x0]) 22 Invalid argument



 Comments   
Comment by Andreas Dilger [ 26/May/16 ]

John's recent comment may also solve this problem

Comment by Andreas Dilger [ 30/May/16 ]

Patch landed for 2.9.0.

Comment by Andreas Dilger [ 06/Jun/16 ]

Reopen to fix resolution type.

Comment by Andreas Dilger [ 06/Jun/16 ]

Close as a duplicate of LU-4781

Generated at Sat Feb 10 02:01:59 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.