[LU-8441] Text file busy error after overwriting file

• Type: Bug
• Resolution: Duplicate
• Priority: Minor
• Affects Version/s: Lustre 2.8.0, Lustre 2.5.5
• Labels: llnl llnlfixready
• Environment: lustre-2.5.5-6chaos_2.6.32_573.26.1.1chaos.ch5.4.x86_64.x86_64
• Severity: 3
• Assignee: Jian Yu
• Reporter: Teresa Kamakea (Inactive)

Description

Here's our reproducer:

sh -c 'cd /p/lscratchd/$USER && (f=toss-3321; rm -f $f; cp /bin/ls $f; od -N1 $f; ./$f; echo > $f; rm -f $f)'

This looks similiar to LU-6232. This affects emacs which is impacting our users. This behaviour is a difference in how xemacs vs. vi deal with files that they already have open. With vi, it always writes to a temporary new file which it then moves over top of the file being edited. With xemacs, the original file is moved to <file>~ and a new file written on the first write. After that it overwrites the new file. One can see this by running them, saving a file, checking the inode number with "ls -i <file>", and then repeating the save and check operations. With xemacs the inode number won't change for each save. With vi, it will.

Issue Links

• duplicates: LU-8019 Openlock breakage
• is duplicated by: LU-7727 open with FMODE_EXEC fails with ETXTBSY after a failed FMODE_WRITE open attempt on a read only client