linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Bertrand Jacquin <bjacquin@exosec.fr>
Cc: linux-nfs@vger.kernel.org
Subject: Re: I/O Wait on exportfs
Date: Tue, 17 Jan 2012 11:40:44 -0500	[thread overview]
Message-ID: <20120117164044.GC13977@fieldses.org> (raw)
In-Reply-To: <20120117154319.GB19990@lady-voodoo.exosec.local>

On Tue, Jan 17, 2012 at 04:43:19PM +0100, Bertrand Jacquin wrote:
> Le mardi 17 janvier 2012 à 16h09, « J. Bruce Fields » a écrit :
> > On Tue, Jan 17, 2012 at 03:29:45PM +0100, Bertrand Jacquin wrote:
> > > For a specific case I have /etc/exports with 1281 entries as I need
> > > mount --bind to be exported to NFS Clients too.
> > 
> > Could you explain what you mean by that?
> 
> In this case, I need /srv/mail to be exported to clients. But for a 1
> month period, I need folders present in /srv/mail2 to be accessible in
> /srv/mail.
> 
> We are moving datas to a SAN, and to avoid modifying any mail configuration
> (and the long list depending on it), I mount /srv/mail2 subdirectory to
> /srv/mailsubdirectory until all subdirectory are migrated :
> 
>  # mount /dev/drbd5 /srv/mail
>  # mount /dev/mapper/iqn.dXX:san1.target0-lun0 /srv/mail2
>  # <moving data from /srv/mail/user1 to /srv/mail2/user1>
>  # mount --bind /srv/mail2/user1 /srv/mail/user1
> 
> To make /srv/mail2/user1 data visible for NFS client, I need to use
> crossmnt options in /etc/exports as nohide is client per client.
> 
> exports(5) say :
> 
>   Thus when a child filesystem "B" is mounted on a parent "A", setting
> 	crossmnt on "A" has the same effect as setting "nohide" on B.
> 
> But I can't say that this had work at all, but adding child filesystem
> in /etc/export, then 'mount -o remount' NFS partition on client fix
> that. I'm maybe wrong, but my tests put me in that way.

That's a bug, it should be enough just to export /srv/mail, and the
mounts underneath should then automatically be exported.

Hm--there have been a couple fixes in that area recently.  You might try
building the most recent nfs-utils.

Then you shouldn't need to list every subexport explicitly in
/etc/exports.

(That may not solve your performance problem, though.)

--b.

> 
> > > Since I have ~1100 entries, reexporting /etc/exports have some bad
> > > effects to connected clients, load rise to ~500 for 4/5 minutes, this is
> > > always reproducible.
> > > 
> > > This was using 'exportfs -ra'. I did try with 'exportfs
> > > 192.168.0.1:/srv/mail/1234' to avoid reexport every directories, and
> > > the sync process but the result is the same.
> > 
> > Does a -t option (see rpc.mountd(8)) help?
> 
> This is interesting
> 
> Bertrand
> 
> -- 
> Bertrand Jacquin, EXOSEC (http://www.exosec.fr/)
> ZAC des Metz - 3 Rue du petit robinson - 78350 JOUY EN JOSAS
> Tel: +33 1 30 67 60 65  -  Fax: +33 1 75 43 40 70
> GSM: +33 6 71 01 70 30  -  mailto:bjacquin@exosec.fr

  reply	other threads:[~2012-01-17 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17 14:29 I/O Wait on exportfs Bertrand Jacquin
2012-01-17 15:09 ` J. Bruce Fields
2012-01-17 15:43   ` Bertrand Jacquin
2012-01-17 16:40     ` J. Bruce Fields [this message]
2012-01-17 16:53       ` Bertrand Jacquin

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=20120117164044.GC13977@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bjacquin@exosec.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).