From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason L Tibbitts III Subject: Re: A weird autofs problem Date: 17 Aug 2007 09:27:11 -0500 Message-ID: References: <1187320655.3560.2.camel@raven.themaw.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1187320655.3560.2.camel@raven.themaw.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: autofs-bounces@linux.kernel.org Errors-To: autofs-bounces@linux.kernel.org To: Ian Kent Cc: autofs@linux.kernel.org >>>>> "IK" == Ian Kent writes: IK> That NFS problem was fixed in 2.6.18 I think. Well, I'm at 2.6.20, so.... IK> Something has changed? I honestly can't think of anything. IK> We'll need you to get a first hand look at a broken system and IK> have a look around and see what really is wrong. And you know that IK> a debug log would be good too. OK, here's a machine that's gone bad. df shows: nas01:/export/users-00/boyarkin - - - - /home/boyarkin Attempting to unmount the directory results in "device is busy" as the user is currently logged in and has files open on the filesystem. Unfortunately because the user has not logged out of this machine, I haven't been able to restart the automounter so debugging is not enabled. Simply running "umount -l /home/boyarkin" as roott causes the mount to appear properly. I've kicked the user out of the machine and restarted the automounter with debugging on. I'll continue to watch this machine and see if the problem reoccurs. - J<