From: Neil Brown <neilb@suse.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Christoph Hellwig <hch@infradead.org>,
nfs@lists.sourceforge.net, "Talpey,
Thomas" <Thomas.Talpey@netapp.com>,
Simon Peter <simon.peter@gmx.de>
Subject: Re: Delays on "first" access to a NFS mount
Date: Thu, 8 Mar 2007 16:42:15 +1100 [thread overview]
Message-ID: <17903.41527.623137.618107@notabene.brown> (raw)
In-Reply-To: message from J. Bruce Fields on Thursday March 8
On Thursday March 8, bfields@fieldses.org wrote:
> On Thu, Mar 08, 2007 at 10:39:23AM +1100, Neil Brown wrote:
> > Imagine having hundreds of filesystems on some sort of library (a CD
> > library?) where each can be identified by a UUID which gets stored in
> > the fsid in the filehandle.
> > Imagine a simple extension to mountd so that a call-out were made when
> > an unknown filehandle arrived. This callout could mount the required
> > filesystem and export it. Maybe the library only allows 3 filesystems
> > to be mounted at a time, so it would unmount the lease-recently-used
> > one.
>
> Maybe. Is this practical? Do we know of any cases of users doing this?
Someone once mentioned doing something vaguely like this... I don't
know the exact details. It was mentioned in the context of the fsid
being too small to do a really good job.
I wonder if you can export autofs to get them mounted in the first
place.....
> Do you block forever if you try to access 4 filesystems at once? I
> dunno....
round-robin? Sending lots of EINPROGRESS for one filesystem while the
others have a turn.
>
> > I have often wanted to write a 'Linux commentary' that explains all
> > the hows and whys of things. I even started some bits once (to help
> > me understand the VFS layer). But Linux changes so fast that any
> > entry in such a commentary would be out-of-date before it was
> > written....
>
> And there's a lot to document. I mean, look:
>
> http://www.oreilly.com/catalog/understandlni/
>
> Just over a thousand pages, just covering the kernel networking code
> (and only some of it at that). Maybe they just lost the forest for the
> trees, but still, yipes.
Is there really a market for that sort of book? Maybe we should write
"Understanding Linux NFS" in our spare time .... oh wait, we don't
have any spare time. Maybe in a couple of decades when I retire:-)
NeilBrown
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-03-08 5:42 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 10:23 Delays on "first" access to a NFS mount Simon Peter
2007-03-07 12:38 ` Talpey, Thomas
2007-03-07 13:22 ` Simon Peter
2007-03-07 15:06 ` Simon Peter
2007-03-07 15:10 ` Simon Peter
2007-03-07 15:42 ` J. Bruce Fields
2007-03-07 18:44 ` Simon Peter
2007-03-07 20:29 ` J. Bruce Fields
2007-03-07 21:46 ` Simon Peter
2007-03-07 22:05 ` J. Bruce Fields
2007-03-07 23:19 ` Simon Peter
2007-03-07 22:09 ` Neil Brown
2007-03-08 15:49 ` Simon Peter
2007-03-09 13:02 ` Simon Peter
2007-03-09 14:59 ` J. Bruce Fields
2007-03-07 20:31 ` Talpey, Thomas
2007-03-07 20:50 ` J. Bruce Fields
2007-03-07 21:07 ` Talpey, Thomas
2007-03-07 21:17 ` J. Bruce Fields
2007-03-07 21:23 ` Talpey, Thomas
2007-03-07 21:54 ` J. Bruce Fields
2007-03-07 22:37 ` Neil Brown
2007-03-07 23:06 ` J. Bruce Fields
2007-03-07 23:39 ` Neil Brown
2007-03-08 5:14 ` J. Bruce Fields
2007-03-08 5:42 ` Neil Brown [this message]
2007-03-08 13:43 ` Olaf Kirch
2007-03-08 21:27 ` J. Bruce Fields
2007-03-09 15:02 ` Olaf Kirch
2007-03-16 21:47 ` Christoph Hellwig
2007-03-16 21:54 ` J. Bruce Fields
2007-03-16 21:57 ` Christoph Hellwig
2007-03-07 23:24 ` J. Bruce Fields
2007-03-07 23:51 ` Neil Brown
2007-03-08 4:36 ` J. Bruce Fields
2007-03-08 13:27 ` Olaf Kirch
2007-03-08 21:46 ` J. Bruce Fields
2007-03-07 22:15 ` Neil Brown
2007-03-07 21:40 ` Simon Peter
2007-03-07 22:17 ` Neil Brown
2007-03-07 22:36 ` Talpey, Thomas
2007-03-07 22:48 ` Neil Brown
2007-03-07 22:56 ` Talpey, Thomas
2007-03-07 22:12 ` Neil Brown
2007-03-07 22:23 ` 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=17903.41527.623137.618107@notabene.brown \
--to=neilb@suse.de \
--cc=Thomas.Talpey@netapp.com \
--cc=bfields@fieldses.org \
--cc=hch@infradead.org \
--cc=nfs@lists.sourceforge.net \
--cc=simon.peter@gmx.de \
/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