Messages in this thread | | | Date | Sat, 27 Feb 1999 15:51:10 -0500 (EST) | From | "Mike A. Harris" <> | Subject | Re: Can't umount after SIGKILL |
| |
On Mon, 22 Feb 1999, Brian Geisel wrote:
>Greetings, > I have found that if I have a process which is running on a mounted >filesystem, and I kill -9 that process, the filesystem is unable to be >umounted. It thinks the filesystem is still in use. /proc/*/cwd includes >nothing in the directory, and all the processes in there were certainly >killed anyway. Is this something that's broken, or should umount allow -f >(whether that's kernel or app I'm also not sure)?
What kernel?
I've had that happen in 2.0.36 several times recently with my CDROM using SCSI emulation.
-- Mike A. Harris Linux advocate GNU advocate Computer Consultant Open Source advocate
News for nerds, stuff that matters: http://slashdot.org
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |