public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Rainer Krienke <krienke@uni-koblenz.de>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
	linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: 2.4.17:Increase number of anonymous filesystems beyond 256?
Date: Mon, 21 Jan 2002 17:54:36 -0500	[thread overview]
Message-ID: <20020121175436.B11889@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1011275640.16596.linux-kernel2news@redhat.com> <200201171855.g0HIt1314492@devserv.devel.redhat.com> <200201181212.g0ICCGq14563@bliss.uni-koblenz.de>
In-Reply-To: <200201181212.g0ICCGq14563@bliss.uni-koblenz.de>; from krienke@uni-koblenz.de on Fri, Jan 18, 2002 at 01:12:16PM +0100

On Fri, Jan 18, 2002 at 01:12:16PM +0100, Rainer Krienke wrote:
> On Thursday, 17. January 2002 19:55, Pete Zaitcev wrote:
> >
> > I am surprised anyone is interested. If you need more than 800
> > mounts I think your system planning may be screwed.

> ease administration we chose the approach to mount each user directory 
> direcly (via automount configured by NIS) on a NFS client where the user 
> wants to access his data. The most 
> important effect of this is, that each users directory is always reachable 
> under the path /home/<user>.

This is not an unusual setup, but normally servers and
workstations do not need to mount enormous number of volumes.
So, I did the same because it's very useful, but I prohibited
~/.forward. Instead, requests for vacation messages were
submitted centrally and processed with the help of /etc/aliases
and automation scripts. This way mailing loops were under control,
and, as a side effect, sending something to a mailing list
did not require the mailserver to mount a gazillion of home
directories in order to fetch ~/.forward for each recipient.

> So I think it would be really good to have at least the option to have more 
> than 256 NFS mounts even if one has to use unsecure ports for this purpose. 

Sure... The thing is, the 1279 mounts that I did is not
even close to being adequate to combat .forward or something
like separate mounted mail spools for large ISPs. You
really need 10,000 of mounts, at which point the whole idea of
anonymous device numbers falls apart.

-- Pete

  parent reply	other threads:[~2002-01-21 22:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1011275640.16596.linux-kernel2news@redhat.com>
2002-01-17 18:55 ` 2.4.17:Increase number of anonymous filesystems beyond 256? Pete Zaitcev
2002-01-18 12:12   ` Rainer Krienke
2002-01-18 19:40     ` H. Peter Anvin
2002-01-20 10:33       ` Rainer krienke
2002-01-20 10:37         ` H. Peter Anvin
2002-01-18 20:33     ` Horst von Brand
2002-01-19 22:07       ` H. Peter Anvin
2002-01-21 22:54     ` Pete Zaitcev [this message]
2002-01-18 12:26   ` Trond Myklebust
2002-01-21 12:40   ` Rainer Krienke
2002-01-22 10:25   ` Rainer Krienke
2002-01-22 10:40     ` Trond Myklebust
2002-01-22 13:08       ` Rainer Krienke
2002-01-22 13:28         ` Trond Myklebust
2002-01-22 15:23           ` Rainer Krienke
2002-01-22 15:40             ` Trond Myklebust
2002-01-22 17:45             ` Pete Zaitcev
2002-01-24  8:58               ` Rainer Krienke
2002-01-24 17:16                 ` Pete Zaitcev
2002-01-24 17:29                   ` Richard Gooch
2002-01-25  7:28                   ` Rainer Krienke
2002-01-25 17:41                     ` Pete Zaitcev
2002-01-25 18:34                       ` Richard Gooch
2002-01-25 18:42                         ` Pete Zaitcev
2002-01-22 19:45           ` Pete Zaitcev
     [not found] <200201171351.g0HDpdK05456@bliss.uni-koblenz.de.suse.lists.linux.kernel>
2002-01-17 17:49 ` Andi Kleen
2002-01-17 13:51 Rainer Krienke

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=20020121175436.B11889@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=krienke@uni-koblenz.de \
    --cc=linux-kernel@vger.kernel.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