Details
-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
-
3
-
9223372036854775807
Description
If open_by_handle_at() is called in O_WRONLY or O_RDWR mode and then the file descriptor is closed, other lustre clients will still report ETXTBSY.
Example:
On cn16
=======
bschubert@cn16 ~>sudo ~/src/test/open-test /mnt/lustre_client-ES24/bschubert/ime/test7 1
Opened /mnt/lustre_client-ES24/bschubert/ime/test7/test7, fd: 4
Closed d: 4
Now on cn41
=========
bschubert@cn41 ~>/mnt/lustre_client-ES24/bschubert/ime//test7
-bash: /mnt/lustre_client-ES24/bschubert/ime//test7: Text file busy
test7 is just any file which has the the execution bit set.
Attachments
Issue Links
- duplicates
-
LU-8585 All Lustre test suites should pass with subdirectory mount
-
- Open
-
- is duplicated by
-
LU-10667 Open by handle and normal open results in incorrect ETXTBSY behavior
-
- Resolved
-
- is related to
-
LU-12661 sanity test_817: FAIL: failed to execute 'true' command
-
- Open
-
- is related to
-
LU-4398 mdt_object_open_lock() may not flush conflicting handles
-
- Resolved
-
I guess I did not read it far enough, yes there's one ETXTBUSY report due to the open lock.
it appears that the name_to_handle_at/open_by_handle_at use nfs-encoded export operation leading to the nfs detecting logic to trigger so the system sort of operates as designed.
It's going to be tricky to separate real nfs from these users I guess and we don't want the extra lock hit when opening the file. I guess the new downgrade logic might help us here to get a bigger lock and then just drop the unneeded bit.