From: Neil Brown <neilb@suse.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: nfs@lists.sourceforge.net, Steve Dickson <SteveD@redhat.com>
Subject: Re: [NFS] nfs-utils crossmnt/fsid bug
Date: Thu, 29 Nov 2007 14:59:21 +1100 [thread overview]
Message-ID: <18254.14617.710446.759398@notabene.brown> (raw)
In-Reply-To: message from J. Bruce Fields on Monday November 26
On Monday November 26, bfields@fieldses.org wrote:
> > When exported a filesystems with option inherited (by the crossmnt
> > option) from a higherlevel filesystem, ignore filesystem specific
> > options like FSID and explicit UUID.
>
> Looks right to me. I'm confused about uuid's--how does the non-explicit
> UUID case work?
Thanks, though on reflection I don't think we need to do the
'stat's. Just checking the path names should be sufficient, but I will
double check.
non-explicit UUIDs are derived using libblkid, typically a UUID out of
the filesystem that is being exported.
The only problem is that it appears that libblkid isn't as efficient
as one might like and if you have hundreds of mounts, mountd can slow
down. I still need to look into that.
NeilBrown
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next prev parent reply other threads:[~2007-11-29 3:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 20:46 nfs-utils crossmnt/fsid bug J. Bruce Fields
2007-11-23 2:50 ` [NFS] " Neil Brown
[not found] ` <18246.16373.177320.570040-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2007-11-26 22:39 ` J. Bruce Fields
2007-11-29 3:59 ` Neil Brown [this message]
2007-12-03 22:51 ` Frank Filz
2007-12-04 1:09 ` Neil Brown
[not found] ` <18260.43206.943331.889058-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2007-12-04 17:42 ` Frank Filz
2007-12-07 19:05 ` Frank Filz
2007-12-11 21:20 ` Frank Filz
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=18254.14617.710446.759398@notabene.brown \
--to=neilb@suse.de \
--cc=SteveD@redhat.com \
--cc=bfields@fieldses.org \
--cc=nfs@lists.sourceforge.net \
/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