Date: Thu, 15 Oct 1998 10:31:55 -0700 (PDT) From: David Wolfskill <dhw@whistle.com> To: dan@dpcsys.com, doug@footech.com Cc: questions@FreeBSD.ORG Subject: Re: qpopper Message-ID: <199810151731.KAA02570@pau-amma.whistle.com> In-Reply-To: <199810151641.JAA25774@srv01.bigwheel.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>Date: Thu, 15 Oct 1998 09:41:23 -0700 (PDT) >From: Doug Jolley <doug@footech.com> >....That >was beacause, much to my surprise, I found that I couldn't >umount either the /var or /usr file systems (or both, I don't >remember). I would get a "device busy" error. I usually >associate that particular error with being logged into the >filesystem that I'm trying to umount; but, I wasn't. I was >logged into the / filesystem. What I wanted to do was to >interactively umount the existing /var and /usr filesystems >and then interactively mount the corresponding file systems >from the primary drive. I'd love to know why I couldn't >umount those file systems. Generally, it means that at least one process is running that has a file or directory on the filesystem open -- for example, the mount point (or one of its sub-directories) could be the "current working directory" of a process. david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810151731.KAA02570>