asked on Can't rm -rf the directory with error being "Text file busy", how to solve it?
This is using a SLES 12. On this SuSE server, we map to a remote CIFS share with the relevant credentials.
This is the cifs mapped share:
//192.168.116.162/DCS cifs 401G 18G 384G 5% /mnt/YTAPxxx-RRR
Browse to /mnt/YTAPxxx-RRR/500000/2021-Jul-13/, there are those updated *.csv files. However, if you attempt to delete (rm) any one of this csv file, the error - rm: cannot remove `lpp_0902.csv': Text file busy.
Ever checked with these commands - lsof | grep -i 2021-Jul-13 or fuser /mnt/YTAPxxx-RRR/500000/2021-Jul-13/, both show none.
What's went wrong with these csv files? how to solve it?
Thanks in advance.
This is the cifs mapped share:
//192.168.116.162/DCS cifs 401G 18G 384G 5% /mnt/YTAPxxx-RRR
Browse to /mnt/YTAPxxx-RRR/500000/2021-Jul-13/, there are those updated *.csv files. However, if you attempt to delete (rm) any one of this csv file, the error - rm: cannot remove `lpp_0902.csv': Text file busy.
Ever checked with these commands - lsof | grep -i 2021-Jul-13 or fuser /mnt/YTAPxxx-RRR/500000/2021-Jul-13/, both show none.
What's went wrong with these csv files? how to solve it?
Thanks in advance.
Linux
Last Comment
SooHow Cheng
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
If a remote system has the file open, it will show as open by some local process (samba, nfs, ...).
OP showed output from df - what is output from mount?
"Text file busy" is usually associated with memory-mapped files
OP showed output from df - what is output from mount?
"Text file busy" is usually associated with memory-mapped files
If I am understanding this correctly, your SLES 12 is mapping a share on some 192.168.116.162 server.
You can only check the open files for your local machine, but the server 192.168.116.162 or other clients using the same share may also (not visible to the SLES) have files open/locked.
The only machine really aware of any open files is 192.168.116.162 - so you have to run lsof (or the equivalent tool on 192.168.116.162) there to really see what process is locking the file.
You can only check the open files for your local machine, but the server 192.168.116.162 or other clients using the same share may also (not visible to the SLES) have files open/locked.
The only machine really aware of any open files is 192.168.116.162 - so you have to run lsof (or the equivalent tool on 192.168.116.162) there to really see what process is locking the file.
then again: is the file actually a csv file? "text file" is also an alias for a program file. if a program is running all files associated with it are locked and cannot be deleted.
So is the file actually a .csv file or a program hiding as a .csv file.
So is the file actually a .csv file or a program hiding as a .csv file.
ASKER
Thanks for both experts, the problem is resolved
ASKER
I really don't know
Seth may gave the answer as the problem could be these files were opened by other parties.
Seth may gave the answer as the problem could be these files were opened by other parties.
lsof might not show anything open there, but that is a remote cifs share and could be open somewhere else that has DCS mounted (or mapped in windows)
suggest looking at the server that hosts that share and see what it shows for open files