Hmm, yes, if you have something on the client using the mount you get
stuck. (Have you tried -o remount? Not that it's a solution really)
> What if we compare in-memory mount data with /etc/exports and refuse to
> remove anything not present in that file and/or not specifically forced
> with a command line flag? Seems easy enough, but perhaps I'm overlooking
> something.
This will not work, as all exports need to be revoked in order for the
server to be able to umount an exported filesystem. If we do this, the
server will not be able to do a clean shutdown. I suppose that if we use
the 'really remove all in-memory exports' on shutdown and remember those
exports across the boot, it could work. It feels messy though, and there
might be race conditions that result in clients breaking if they issue a
request just before shutdown or just after boot.
What I see as a possible solution (though not necessarily easy to implement) is to have knfsd ask mountd what to do with any getfh for something that is not in the in-memory export list.
Regards,
/Anders
-- -- Of course I'm crazy, but that doesn't mean I'm wrong. Anders Hammarquist | Mud at Kingdoms | iko@netg.se NetGuide Scandinavia | telnet kingdoms.se 1812 | Fax: +46 31 50 79 39 http://www.netg.se | | Tel: +46 31 50 79 40
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/faq.html