[LU-6232] Text file busy error -- lustre 2.6.0 client

• Type: Bug
• Resolution: Fixed
• Priority: Major
• Affects Version/s: Lustre 2.6.0, Lustre 2.4.2, Lustre 2.7.0

Environment

- Client mainline kernel 3.12.5 with patches (mentioned in LU-4400) / lustre-utils 2.4.2
- Servers lustre 2.4.2/ZFS OSDs and 2.4.2/ldiskfs OSDs
- ko2iblnd an ksocklnd

• Severity: 3
• Assignee: WC Triage
• Reporter: Yan Burman

Description

When executing the following simple script, the in-kernel client fails with error "Text file busy", while the out-of-kernel 2.4.2 client compiled against 2.6.32 vanilla works.

-----------
#!/bin/bash

rm -f ./test.sh
touch ./test.sh && chmod a+x ./test.sh
echo "echo foo" > ./test.sh
./test.sh
echo "echo foo" > ./test.sh
------------

The following script works in all cases:

-----------
#!/bin/bash

rm -f ./test.sh
touch ./test.sh && chmod a+x ./test.sh
echo "echo foo" > ./test.sh
bash ./test.sh
echo "echo foo" > ./test.sh
------------

Issue Links

• is related to: LU-4398 mdt_object_open_lock() may not flush conflicting handles
• is related to: LU-4429 clients leaking open handles/bad lock matching in ll_md_blocking_ast

Comments

[Scott Nolin (Inactive)]

While this is a bug with an easy workaround, it's such a basic thing I'm surprised it's not addressed.

It definitely exists in 2.7, and we'll test 2.8 soon.

While not dangerous, it generates some amount of confusion and help requests.

[Yan Burman]

This bug is present in lustre 2.6.0. I tried applying the attached patch, but it does not apply since LU4429 is already in 2.6.0

Please advise