On Thu, 2008-12-04 at 14:13 +0100, Martin Vogt wrote:
>
> Hello list,
>
> I'm currently experimenting with autofs on SuSE 11.1 rc1
>
> -autofs-5.0.3-82.19
I don't know what this means in terms of patches applied, but ok.
>
> Around the 1024th mount, autofs hangs and the machine needs a reboot -f.
>
> I have here >2000 mount points which usually look like this:
>
> /homes/vogt0001 --fstype=bind :/net/fsA/home/user/vogt0001
> /homes/vogt0002 --fstype=bind :/net/fsB/home/user/vogt0002
> [..]
> /homes/vogt2000 --fstype=bind :/net/fsC/home/user/vogt2000
So a direct map?
With many active real mounts, is that what you're saying?
>
>
> Further debugging revealed:
>
> pxe1:/home/demo1 # lsof -p <automount pid>
> [...]
> automount 5111 root 1022r DIR 0,228 0 13029 /u/itwm/hinojosa
> automount 5111 root 1023r DIR 0,561 0 13362 /u/itwm/andrejs
> automount 5111 root 1024r FIFO 0,7 0t0 26910 pipe
>
> The 1024 really looks like some limit, which is hit by the automount
> process.
Quite possibly, but I don't think there is anything autofs can do about
it since in autofs we see:
...
#define MAX_OPEN_FILES 10240
...
rlim.rlim_cur = MAX_OPEN_FILES;
rlim.rlim_max = MAX_OPEN_FILES;
res = setrlimit(RLIMIT_NOFILE, &rlim);
if (res)
warn(logging,
"can't increase open file limit - continuing");
Unless I've not got this correct in some way the open file limit should
be much higher. But there are ways the OS configuration can limit this.
>
> I checked ulimit -a:
>
> pxe1:/home/demo1 # ulimit -a
> core file size (blocks, -c) 0
> data seg size (kbytes, -d) unlimited
> scheduling priority (-e) 0
> file size (blocks, -f) unlimited
> pending signals (-i) 16117
> max locked memory (kbytes, -l) 64
> max memory size (kbytes, -m) 1717680
> open files (-n) 4096
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority (-r) 0
> stack size (kbytes, -s) 8192
> cpu time (seconds, -t) unlimited
> max user processes (-u) 16117
> virtual memory (kbytes, -v) 2455520
> file locks (-x) unlimited
>
>
> The I checked ulimit under /proc:
>
> pxe1:/proc/5111 # cat limits
> Limit Soft Limit Hard Limit Units
> Max cpu time unlimited unlimited
> Max file size unlimited unlimited
> Max data size unlimited unlimited
> Max stack size 8388608 unlimited
> Max core file size unlimited unlimited
> Max resident set 1758904320 unlimited
> Max processes 16117 16117
> Max open files 10240 10240
> Max locked memory 65536 262144
> Max address space 2514452480 unlimited
> Max file locks unlimited unlimited
> Max pending signals 16117 16117
> Max msgqueue size 819200 819200
> Max nice priority 0 0
> Max realtime priority 0 0
> Max realtime timeout unlimited unlimited
>
>
> ==> At least the Max file desc. looks ok, but somewho it hangs.
> Ah, the behavoir by autofs is:
>
> - It hangs on duing a mount operation:
>
> root 5111 0.0 0.1 97200 2936 pts/0 Sl+ 13:30 0:01
> /usr/sbin/automount -d -f -t 600 -p /var/run/automount.pid -O ro
> root 9541 0.0 0.0 0 0 pts/0 Z+ 13:31 0:00 [mount]
> <defunct>
So maybe mount(8) and its relatives are the problem, not sure I can do
much about that either.
>
> stopping automount is not possible it needs a reboot -f
>
> I have search a bit for this problem, but found no solution yet.
>
>
> regards,
>
> Martin
>
>
> PS: I havent found a way to do it without bind mounts
>
>
>
>
>
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs
_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs
