[LU-158] Lock test of connectathon failed

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 2.1.0
• Fix Version/s: Lustre 2.1.0
• Type: Bug
• Priority: Minor
• Reporter: Sarah Liu
• Assignee: Oleg Drokin
• Resolution: Fixed
• Severity: 3

Description

running connectathon on three lustre clients, basic,general and special tests passed, lock test failed.

test log
------------
Starting LOCKING tests: test directory /mnt/lustre/d0.connectathon (arg: -f)

Testing native post-LFS locking

Creating parent/child synchronization pipes.

Test #1 - Test regions of an unlocked file.
Parent: 1.1 - F_TEST [ 0, 1] FAILED!
Parent: **** Expected success, returned errno=38...
Parent: **** Probably implementation error.

• • PARENT pass 1 results: 0/0 pass, 0/0 warn, 1/1 fail (pass/total).

• • CHILD pass 1 results: 0/0 pass, 0/0 warn, 0/0 fail (pass/total).
    lock tests failed
    parallel-scale test_connectathon: @@@@@@ FAIL: connectathon failed: 1

Comments

[Oleg Drokin]

errno 38 is ENOSYS which means you forgot to mount lustre client with -o flock option which is required if you want locking to actually work.

[Peter Jones]

Yu Jian

Could you look into this one please?

Thanks

Peter

[Sarah Liu]

I have tried with mount option flock, it works, so close this bug.