Re: nfs4 filesystem mounted via the "bind" option reports wrong fstype

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/27/2007 9:32:42 PM +0200, "J. Bruce Fields" <[email protected]> wrote:
On Mon, Aug 27, 2007 at 08:15:07PM +0100, Al Viro wrote:
On Mon, Aug 27, 2007 at 02:40:59PM -0400, J. Bruce Fields wrote:
There's no reason not to just mount server:/exports/data directly at
/home/data; the bind mounts are just a workaround for the somewhat
primitive exports facility on the server side.
Bullshit.  Bindings are first-class operations on _client_, regardless
of fs types involved.

I know.  Did I say something to the contrary?

Maybe I was too terse; in more detail: the original poster appears to be
mounting server:/exports/data by first mounting server:/ somewhere and
then bind-mounting the exports/data someplace else.  I couldn't see an
obvious reason they'd be using two steps instead of just performing a
single mount of server:/exports/data.

So my assumption was that this was due to a confused memory of some
server-side setup instructions. (On the server side, nfs4 export setup
often requires the administrator to do some extra bind mounts which
shouldn't really be necessary.)

Right. When setting up the clients, I remembered these "bind" mount things, and applied the same client-side because at this time I had other bugs for which I thought "bind" mount was the solution. In fact it's not, but as nfs4 is seen as a unique filesystem and I had several exported volumes, It was easier to mount the nfsv4 pseudoroot, then "bind" mount all the volumes from it.

But the bug's still here, and since these additional mounts appear "magically" in /proc/mounts, I don't know where to look at in the kernel source. The nfsv4 client code must have somewhere a kind of nfs4 automounter for "nohide" volumes. A bit ugly IMHO, but the only way to show quotas for separates nfsv4 exported volumes too.

Gabriel
-
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/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux