All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Dennis Jacobfeuerborn <d.jacobfeuerborn@conversis.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: bind mounts, crossmnt and multi client nfsv3
Date: Mon, 21 Mar 2011 14:09:23 +1100	[thread overview]
Message-ID: <20110321140923.5a618d89@notabene.brown> (raw)
In-Reply-To: <4D86B6F2.1070004@conversis.de>

On Mon, 21 Mar 2011 03:24:50 +0100 Dennis Jacobfeuerborn
<d.jacobfeuerborn@conversis.de> wrote:

> Hi,
> I have a storage system that is exporting many directories to multiple 
> clients resulting in a lot of mountpoints (156) on each client. What I'm 
> trying to do is to create a single directory on the server and then use 
> mount --bind to mount all the different directories (which are stored on 
> different LVM volumes) into this single export directory and finally export 
> this directory to the clients.
> Now the exports man-page mentions the crossmnt option but it also mentions 
> that it cannot be used if I want to export the directory to multiple 
> clients. Is there another way to accomplish something like this?
>

Just export the top directory with 'crossmnt' - it should work fine.

The 'multiple clients' thing only affects 'nohide' and I think it only
affected it back in 2.4 days.
Lots changed with 2.6, but maybe not enough of the man page changed :-(

So try with 'crossmnt' and if it doesn't work, then come back with details.

NeilBrown


  reply	other threads:[~2011-03-21  3:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21  2:24 bind mounts, crossmnt and multi client nfsv3 Dennis Jacobfeuerborn
2011-03-21  3:09 ` NeilBrown [this message]
2011-03-21 12:27   ` Dennis Jacobfeuerborn
2011-03-21 17:25     ` J. Bruce Fields
2011-03-21 17:53       ` Dennis Jacobfeuerborn
2011-03-21 18:19         ` J. Bruce Fields
2011-03-21 19:04           ` Dennis Jacobfeuerborn
2011-03-22 17:43             ` Dennis Jacobfeuerborn
2011-03-22 17:54               ` J. Bruce Fields

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110321140923.5a618d89@notabene.brown \
    --to=neilb@suse.de \
    --cc=d.jacobfeuerborn@conversis.de \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.