Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!sci34hub!gary From: gary@sci34hub.UUCP (Gary Heston) Newsgroups: comp.unix.i386 Subject: Re: Cannot umount /usr filesystem (ALWAYS "busy") Message-ID: <681@sci34hub.UUCP> Date: 29 Jun 90 19:09:34 GMT References: <267@jorel.UUCP> <248@harper.UUCP> Reply-To: gary@sci34hub.sci.com (Gary Heston) Distribution: usa Organization: SCI Technology, Inc., Huntsville, Al. Lines: 20 In article <248@harper.UUCP> brad@harper.UUCP (Brad Cleghorn) writes: >I have found that if my home dir is in /usr, and I'm logged in, (no >matter *what* my pwd is) /usr won't umount -- Even if I'm su. I had >to log in on the console port as root. Yes, any logged-in users' home directory is considered "open", and the filesystem is therefore busy. This applies to daemon processes as well, like "lp", "cron", and "uucp". If you have any of those running, /usr will refuse to umount for the same reason. Create a file structure /u, add a userid into it, and log in under it. Then try to umount it, even as root--it won't. You can umount /usr as root because roots' home directory is "/", so /usr doesn't have any "open" files or directories. -- Gary Heston { uunet!sci34hub!gary } System Mismanager SCI Technology, Inc. OEM Products Department (i.e., computers) "The esteemed gentleman says I called him a liar. That's true, and I regret it." Retief, a character created by Keith Laumer.