Message-ID: <4CBC74E8.7070801@panasas.com>
Date: Mon, 18 Oct 2010 18:25:12 +0200
From: Boaz Harrosh <bharrosh@panasas.com>
To: Jesper Krogh <jesper@krogh.cc>
CC: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: lsof and open files from the nfs-server
References: <4CB62095.4010708@krogh.cc>
In-Reply-To: <4CB62095.4010708@krogh.cc>
Content-Type: text/plain; charset=UTF-8
Sender: linux-nfs-owner@vger.kernel.org
MIME-Version: 1.0

On 10/13/2010 11:11 PM, Jesper Krogh wrote:
> Hi.
> 
> Quite often when you have to umount a fileshare you get the
> message "Device or resource busy". Typically I traverse through
> the output of lsof | grep mountpoint and stop processes or kill
> until I can safely umount.
> 
> But the nfs-kernel-server does not register its open files, so
> seen from userspace is it extremely hard to find out that is actually
> is the nfs-server that prevents you from being able to umount
> the filesystems.
> 
> Would it be possible to register the open files the same place
> so administrators can see them?
> 
> ... basically just a feature-request from one who just spend an hour on 
> that.
> 

Me to!

Also note that even if there are no open files in clients
and no client mounts on the server, but there where in the
passed. The used to be used super-block is referenced. Only
restart of the nfs service will release it.

But yes if it could register as a special file for lsof to
see it would help a lot.

Boaz