On Fri, 2007-08-31 at 15:12 +0200, Frank van Maarseveen wrote:
> IMHO I'd only consider returning EBUSY when trying to mount _exactly_
> the same directory with different flags, not for arbitrary subtrees. The
> client should preferably not be bothered with server side disk
> partitioning (at least not beyond the obvious such as df output).
That is utterly inconsistent and confusing too.
If you have a filesystem "/foo" exported on the server "remote", then
why should
mount -oro remote:/foo
mount -orw remote:/foo/a
be allowed, but
mount -oro remote:/foo
mount -orw remote:/foo
be forbidden? The caching problems are the same. Telling the admin that
one is safe and the other is not, is just messing with his mind.
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
