autofs / 2.0.34

Mark A. Bentley (bentlema@cs.umn.edu)
Wed, 15 Jul 1998 09:14:56 -0500 (CDT)


There seems to be an expiration bug with autofs / 2.0.3x kernels. I'm
using autofs-3.3.1, mount-2.7l, and linux 2.0.34, and have seen this
problem with other 2.0.3x kernels.

The problem is, autofs expires the mount, and attempts to unmount the
filesystem. (These are all NFS mounts). /etc/mtab gets updated, but
/proc/mounts still thinks the filesystem is mounted.

I don't know if this is a bug in mount, proc, or autofs?

Also, is there a way to increase the number of mountable filesystems?
Right now, I can mount about 45 filesystems (a combination of ext2 and
NFS), but then I get the following error:

mount(nfs): nfs: mount failure yogi:/export/yogi01 on /home/yogi01
>> mount: wrong fs type, bad option, bad superblock on yogi:/export/yogi02,
>> or too many mounted file systems

This error message also results after long uptimes, since /proc/mounts
tends to accumulate info about mounted filesystems that arn't really
mounted, so mount complains.

If anyone is interested in looking into fixing this bug, I'd be glad to
offer assistance on the testing side. I can very easily re-produce these
results.

<OFF TOPIC>
We've been running Linux here at the U of Minn. for 3 years. Our current
install base it up to about 100.
</OFF TOPIC>

==========================================================================
Mark A Bentley Email: bentlema@cs.umn.edu
Systems Staff, CSci Dept
University of Minnesota URL: http://www.cs.umn.edu/~bentlema/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html