Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Hod do you kill a mount command if kill -9 doesn't work?

Status
Not open for further replies.

scoobs

Instructor
Aug 5, 2002
17
US
I am using a mount command in a script to load a file(s) from a CD and if it doesn't work we have to reboot the system to get the mount command to go away. How can I kill a mount process when the kill -9 does not work?
 
I am trying to load a file from the cd onto the SCO Unix server and the script doesn't complete so the end user breaks out of the script and the mount command is still running. I try a kill -9 and it does not stop the process. Any suggestions?
 
I just don't understand why it hangs if there's no CD?
Call SCO and tell them they need to fix this. It's not supposed to do that.

Cheers

 
There is a file on the CD. It is not loading the file onto the system and is hanging. That is the exact problem.
 
I had a similar problem today with linux-2.6.4 and inappropriate settings in fstab:
Code:
/dev/hda3 / reiserfs ... 1 1
# instead of 
/dev/hda3 / reiserfs ... 0 0
Perhaps you have problems with fstab?
 
it may be mount parameters used.....
check /etc/default/filesys in SCO Openserver for something trying to automount the cd.
What kind of filesystem is on the cd? how are you trying to mount it?

once a process has gone zombie then only a restart will clear it.
 
Hi all,

Immortal processes can be created when a process running at higher than normal priority gets hung up waiting on device I/O. You can try to renice the process and make another attempt to kill it, or you can try to SIGHUP the parent process (I'm guessing the parent process started out as a shell, and then switched to init once the shell died). Neither of these steps are guaranteed to work.

I want to point out that mount probably has some critical system resources locked, and killing the process with the lock in place may lead to undefined behavior.

-Jason

 

try this:

fuser -cu directory/file
fuser -fu directory/file
fuser -k directory/file ( this will kill any user who use the directory i think )
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top