On Mon, Oct 18, 2010 at 06:25:12PM +0200, Boaz Harrosh wrote: > 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. So what does lsof do, scan /proc/? Does it make sense to have proc entries for kernel threads? Is there any other subsystem that does this kind of thing? --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
