Based on some of your comments I tried to find what was the issue with the "umount"
The below command helped me to get the information who is holding the lock so based on Serge Hallyn (serge-hallyn) request the error shows as follows, (lsof didn't help me much here so I used fuser)
USER PID ACCESS COMMAND
/tmp/tmp4WlrLItmpfs: root kernel mount /tmp/tmp4WlrLItmpfs
-----------------------------------------------------------------------------------------------------------------
Based on the above information where I can not kill the PID becuase "kernel" is holding the lock.
Hi
Based on some of your comments I tried to find what was the issue with the "umount"
The below command helped me to get the information who is holding the lock so based on Serge Hallyn (serge-hallyn) request the error shows as follows, (lsof didn't help me much here so I used fuser)
------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- -
# fuser -f -v /tmp/tmp4WlrLItmpfs
/tmp/tmp4WlrLIt
-------
Based on the above information where I can not kill the PID becuase "kernel" is holding the lock.
So what would be my option here?
Thanks