/autofs-5.0.1-0.rc2.152.el5/
Unfortunately, this version doesn't help ...
Thanks
James Pearson
___
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs
passes the date
stamp of the mount point), the automount of file systems in the NIS map
works fine.
Is it possible to get a copy of the autofs RPM for RHEL-5.7 to test?
Thanks
James Pearson
___
autofs mailing list
autofs@linux.kernel.org
http
the creation date of the map mount point is in the future? - but works
fine when the same NIS map is referenced directly from /etc/auto.master?
James Pearson
___
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs
for mount (nfsmount.c, part of util-linux v2.12) has the
comment:
/* timeo is filled in after we know whether it'll be TCP or UDP */
Can I assume, in this case, the value of timeo will be a suitable value
for tcp mounts?
Thanks
James Pearson
I'm seeing a very similar problem on clients using a 2.4.30 kernel (with
the 20041227 autofs4 patch) - do you (or anyone else) know if this patch
will work on 2.4.x clients? The code this patch touches appears to be
identical in the 2.4.x autofs4 source.
Thanks
James Pearson
Jeff Moyer
/auto.data file contains something like:
node2 [options] 192.168.101.2:/node2
node3 [options] 192.168.101.3:/node3
node4 [options] 192.168.101.4:/node4
on machine node2, /data/node2 will be a bind mount (not over NFS) of
/node2 - all the other /data/nodeX mounts will be over NFS.
James Pearson
guarantees that
nothing gets truncated. I have a system up and running that works fine
with about 2500 mounts.
seq_file support for /proc/mounts was introduced with 2.4.19
James Pearson
___
autofs mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman
James Pearson wrote:
There was a long thread a few months ago about this subject:
http://marc.theaimsgroup.com/?t=10633268334r=1w=2
and
http://marc.theaimsgroup.com/?t=10634001356r=1w=2
I've read the posts but as far as I can tell, I can't find a 'solution'
to the problem
Trond Myklebust wrote:
På fr , 21/05/2004 klokka 11:44, skreiv James Pearson:
We've been running this patch on over 400 machines for the last 10 or so
days, and have not seen any instance of this 'VFS: Busy inodes after
unmount/Oops' problem above - previously, we would have seen
, umount or some
other user application.
Is there a 'fix' for this problem?
Thanks
James Pearson
___
autofs mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo/autofs
adverse effects - and also stop the 'permission
denied' my problem ...
James Pearson
James Pearson wrote:
What would be the side effects of dropping the RPC call? I guess the
rpc.mountd on the server will never get a umount request - will this
cause problems with the client autofs repeatedly
and the client autofs 4.0.0pre10
Could there be a case where automount tells the server it's umounting a
mount, but then finds it can't actually do the umount?
James Pearson
___
autofs mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo
-browse', like Solaris amd, but it doesn't seem
right.
Thank you in advance,
Roman.
You could have a look at Ian Kent's 'ghost' patches to autofs v4 via:
http://www.mail-archive.com/autofs@linux.kernel.org/msg02284.html
James Pearson
There is also an archive at:
http://www.mail-archive.com/autofs%40linux.kernel.org/
James Pearson
[EMAIL PROTECTED] wrote:
hi ya james
is there another archive ??? ( that i dont know about ?? )
i keep a (annually-created) single file archive ...
http://www.Linux-Consulting.com
Any chance of making your changes available?
James Pearson
Kent, Ian I. wrote:
H. Peter Anvin wrote:
It's not the browsing that's the big problem (assuming the key database
is enumerable, which not all of them are.) Rather, it's the ls -l
mounts everything issue, which requires
updated - see:
http://marc.theaimsgroup.com/?l=linux-nfsm=101830833827454w=2
James Pearson
James Pearson wrote:
An update to my previous update ...
It looks like this problem is actually a server problem - I get similar
problems on SGI IRIX clients (directory access results is an 'I/O
error
clients
had exactly the same problem at the same time.
Would other NFS client patches improve matters?
Thanks
James Pearson
James Pearson wrote:
Since sending my original message, I've found something on the kernel
list about a similar situation - see:
http://www.geocrawler.com
problem, but currently i can't imagine a
scenario including unavailable NFS-servers, that leads to this permission
denied error.
Could what is described be the problem?
Is there a fix?
Thanks
James Pearson
James Pearson wrote:
I'm using autofs4 (autofs-4.0.0pre10) to mount a number of NFS
for these mounts in mtab) - is this likely to cause
problems/confusion with automount?
Thanks
James Pearson
19 matches
Mail list logo