Skip to contentSkip to conversation

more than 1024 mounts ==>hangs

DISCUSSION Martin Vogt 3 participants 10 messages Dec 4, 2008 – Dec 9, 2008 1 message not in the archive Kernel automounter

lore
Share & tools
lore
#0 lore raw

Hello list,

I'm currently experimenting with autofs on SuSE 11.1 rc1

-autofs-5.0.3-82.19

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

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.

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>

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

maintainer
#1 lore raw
Quoted 6 lines · Martin Vogt

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.

Quoted 9 lines

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?

Quoted 4 lines

Further debugging revealed:

Quoted 8 lines

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.

Quoted 47 lines

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:

Quoted 6 lines

- 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.

Quoted 21 lines

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
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs

#2 lore raw

Hello Ian,

Quoted 7 lines · Ian Kent
Quoted 4 lines · Martin Vogt

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.

Just checked the source rpm from suse:

autofs-5.0.3.tar.bz2

patches:
autofs-5.0.3-upstream-patches-20080806.bz2
autofs-5.0.1-mount_xdr_no_strict_aliasing.patch
autofs-5.0.2-use_local_cflags.patch
autofs-5.0.3-link_kerberos.patch

But I can use an offical release, if you think this is usefull...

Quoted 2 lines

So a direct map?
With many active real mounts, is that what you're saying?

Yes.
I have a bunch of fileservers here, which I like to have mounted under /net/fileserver<XYZ>/

Upon this I have a "virtual filesystem"

/homes/auser0001
/homes/buser0001
...
/homes/yuser1999
/homes/zvogt2000

(which holds all users from all fileserver ~500)

Then I have another virtual filesytem, which groups the users by departments.

eg
/dep/foo/auser0001
/dep/foo/buser0002
[..]
/dep/bar/yuser1999
/dep/bar/zvogt2000

Thus I hit 1000 mounts (500 in homes and 500 grouped in departements-- all bind mounts from /net)

==> 1000 mounts in the case a user issuses a find / for example

Then I have some other fileservers etc... Jumping over 1024 mounts easily...

The mount maps are all direct:
auto.master:

/-      /etc/auto.user
/-      /etc/auto.homes
/-      /etc/auto.deps
/-      /etc/auto.misc

sample auto.homes:

/homes/vogt -fstype=bind,ro :/net/fs42/home/user/vogt

and auto.deps is

/dep/it/vogt -fstype=bind,ro :/net/fs42/home/user/vogt

I didnt find out how to make it without bind mounts.

==> dont know if there is a more elegant solution :(

Around the 1024 mounts I then hit the problem.

Quoted 7 lines
Quoted 2 lines

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

Yes. I think autofs has enough FDs, but the 1024 looks suspicious, I simply have no clue how to debug it.

Quoted 4 lines

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.

The proc entry for the automount process should give the real constrains for the process:

Quoted 25 lines
Quoted 14 lines

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
Quoted 9 lines
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
Quoted 2 lines

So maybe mount(8) and its relatives are the problem, not sure I can do much about that either.

The mount process which gets the exec from automount is a zombie process when it hangs.

Quoted 2 lines

root 9541 0.0 0.0 0 0 pts/0 Z+ 13:31 0:00
[mount] <defunct>

When the compo autofs/mount hangs, I can still issue a bind mount on the command line, with success.

eg:

mount -t bind /net/fs42/home/user/vogt /mnt/tmp1

works.

(Because of this still working, I think that the problem is more on the autofs side)

Do you think the source for "mount" could be helpfull? (Maybe adding some syslogs/printfs to the mount code?)

regards,

Martin

maintainer
#3 lore raw
Quoted 15 lines · Martin Vogt

Hello Ian,

Quoted 7 lines · Ian Kent
Quoted 4 lines · Martin Vogt

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.

Just checked the source rpm from suse:

autofs-5.0.3.tar.bz2

Quoted 7 lines

patches:
autofs-5.0.3-upstream-patches-20080806.bz2
autofs-5.0.1-mount_xdr_no_strict_aliasing.patch
autofs-5.0.2-use_local_cflags.patch
autofs-5.0.3-link_kerberos.patch

But I can use an offical release, if you think this is usefull...

Not sure about that.
Well return to that later.

Quoted 28 lines
Quoted 3 lines

So a direct map?
With many active real mounts, is that what you're saying?

Yes.
I have a bunch of fileservers here, which I like to have mounted under /net/fileserver<XYZ>/

Upon this I have a "virtual filesystem"

/homes/auser0001
/homes/buser0001
...
/homes/yuser1999
/homes/zvogt2000

(which holds all users from all fileserver ~500)

Then I have another virtual filesytem, which groups the users by departments.

eg
/dep/foo/auser0001
/dep/foo/buser0002
[..]
/dep/bar/yuser1999
/dep/bar/zvogt2000

Quoted 4 lines

Thus I hit 1000 mounts (500 in homes and 500 grouped in departements-- all bind mounts from /net)

==> 1000 mounts in the case a user issuses a find / for example

Yeah, that's a pain.

Quoted 2 lines

Then I have some other fileservers etc... Jumping over 1024 mounts easily...

There are two things of concern here.

First, until recently we've had no choice but to retain an open file handle for each active direct mount. Even though the most recent kernel update will provide for the ability to not keep these file handles open the changes to the daemon to achieve this will be difficult especially since we need to retain backward compatibility with kernels that don't have the update. So this aint gonna happen any time soon.

The second thing is that this open file limit shouldn't be happening. I'm pretty sure that, because of the way autofs works, these mounts should be happening in the context of the automount program not the user that has triggered the mount so the limit shouldn't be there.

Quoted 26 lines

The mount maps are all direct:
auto.master:

/-      /etc/auto.user
/-      /etc/auto.homes
/-      /etc/auto.deps
/-      /etc/auto.misc

sample auto.homes:

/homes/vogt -fstype=bind,ro :/net/fs42/home/user/vogt

and auto.deps is

/dep/it/vogt -fstype=bind,ro :/net/fs42/home/user/vogt

I didnt find out how to make it without bind mounts.

==> dont know if there is a more elegant solution :(

Around the 1024 mounts I then hit the problem.

Quoted 3 lines
Quoted 2 lines

The 1024 really looks like some limit, which is hit by the automount process.

Quoted 7 lines
Quoted 4 lines

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

Yes. I think autofs has enough FDs, but the 1024 looks suspicious, I simply have no clue how to debug it.

I'm not sure either, perhaps others on the list will have suggestion?

Quoted 50 lines
Quoted 5 lines

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.

The proc entry for the automount process should give the real constrains for the process:

Quoted 25 lines
Quoted 14 lines

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
Quoted 9 lines
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
Quoted 2 lines

So maybe mount(8) and its relatives are the problem, not sure I can do much about that either.

The mount process which gets the exec from automount is a zombie process when it hangs.

Quoted 2 lines

root 9541 0.0 0.0 0 0 pts/0 Z+ 13:31 0:00
[mount] <defunct>

When the compo autofs/mount hangs, I can still issue a bind mount on the command line, with success.

eg:

mount -t bind /net/fs42/home/user/vogt /mnt/tmp1

Quoted 7 lines

works.

(Because of this still working, I think that the problem is more on the autofs side)

Do you think the source for "mount" could be helpfull? (Maybe adding some syslogs/printfs to the mount code?)

Perhaps, I haven't got time to go into this at the moment but later I could have a look.

A debug log may be useful.
Have a look at http://people.redhat.com/jmoyer for information about how to do this.

Ian

#4 lore raw
In reply to Ian Kent
Quoted 48 lines · Ian Kent
Quoted 6 lines · Martin Vogt

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.

Quoted 9 lines

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?

Quoted 4 lines

Further debugging revealed:

Quoted 8 lines

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");
Quoted 2 lines

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'm pretty sure root processes bypass the max open fds check.

[snip]

Quoted 11 lines
Quoted 8 lines

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.

Yeah, strange. Can we figure out what the mount commandline was for this zombie?

-Jeff

maintainer
#5 lore raw
Quoted 66 lines · Jeff Moyer
Quoted 48 lines · Ian Kent
Quoted 6 lines · Martin Vogt

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.

Quoted 9 lines

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?

Quoted 4 lines

Further debugging revealed:

Quoted 8 lines

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");
Quoted 2 lines

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'm pretty sure root processes bypass the max open fds check.

[snip]

Quoted 9 lines
Quoted 8 lines

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>

Quoted 5 lines
Quoted 2 lines

So maybe mount(8) and its relatives are the problem, not sure I can do much about that either.

Yeah, strange. Can we figure out what the mount commandline was for this zombie?

You would need to enable debug logging.
autofs and syslog setup instructions for this can be seen at
http://people.redhat.com/jmoyer.

Quoted 2 lines

-Jeff

A message that is not in the archive (sent off-list or not yet received): [email protected]

#7 lore raw
Quoted 12 lines · Martin Vogt
Quoted 4 lines · Ian Kent

You would need to enable debug logging.
autofs and syslog setup instructions for this can be seen at
http://people.redhat.com/jmoyer.

I think I can simply start it with "-d" ?.
As from the page this logging is meant to be used when the daemon ist started without debugging, but I can start it directly and can directly hang autofs.

Quoted 5 lines

Hm, I think I will write a small script for you, which lets you simply reproduce this behaviour.

(A script with 2000 direct bind mount :)

Hello list,

the following script:

#!/bin/sh
NET=/net/pxe1/var/tmp
for i in seq 1 2025 ; do

    echo "/homes/vogt${i} -fstype=bind,ro :${NET}"

done

creates a direct mount map with 2025 direct mount.
(I assume you know how to configure autofs how to use this map :) (Please really use a remote host for the mounts when you trigger it, for "localhost" you will find another bug, but currently I'm focused on the remote part, so really use a remote machine here)

Then run a find . -maxdepth 2 to really trigger the mounts. These are the bugs:

- SuSE 11.1 rc1 hangs on the 1024th mount(autofs-5.0.3+patches)
- RHEL52 works (autofs-5.0.1-rc1) on mounting
- RHEL52 has a kernel panic on unmounting (see screenshot attachment)

(started with: automount -d -f -t 600 )

For the kernel panic I started automount in the forground and hit CTRL-C when it was done with mounting, then after a long time, when it tries to umount the mounts it gives the kernel panic.

regards,

Martin

_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs

maintainer
#8 lore raw
Quoted 35 lines · Martin Vogt
Quoted 12 lines · Martin Vogt
Quoted 4 lines · Ian Kent

You would need to enable debug logging.
autofs and syslog setup instructions for this can be seen at
http://people.redhat.com/jmoyer.

I think I can simply start it with "-d" ?.
As from the page this logging is meant to be used when the daemon ist started without debugging, but I can start it directly and can directly hang autofs.

Quoted 5 lines

Hm, I think I will write a small script for you, which lets you simply reproduce this behaviour.

(A script with 2000 direct bind mount :)

Hello list,

the following script:

#!/bin/sh
NET=/net/pxe1/var/tmp
for i in seq 1 2025 ; do

    echo "/homes/vogt${i} -fstype=bind,ro :${NET}"

done

creates a direct mount map with 2025 direct mount.
(I assume you know how to configure autofs how to use this map :) (Please really use a remote host for the mounts when you trigger it, for "localhost" you will find another bug, but currently I'm focused on the remote part, so really use a remote machine here)

Quoted 6 lines

Then run a find . -maxdepth 2 to really trigger the mounts. These are the bugs:

- SuSE 11.1 rc1 hangs on the 1024th mount(autofs-5.0.3+patches)
- RHEL52 works (autofs-5.0.1-rc1) on mounting
- RHEL52 has a kernel panic on unmounting (see screenshot attachment)

Looks like a known issue.

Fixed in patch series included in 2.6.27 (but there was one additional bug fix, not related to this issue, that is included in 2.6.28).

There is no need to log a bug against RHEL-5.2 for this as the 2.6.27 (and the bug fix mentioned above) update has been ported to the RHEL kernel and will be included in 5.3.

The patch series has been posted to this list and the commit history can be viewed in git for upstream kernels so other vendors will need to decide for themselves any action they may wish to take regarding this. In fact there are several issues fixed in the update.

Quoted 17 lines

(started with: automount -d -f -t 600 )

For the kernel panic I started automount in the forground and hit CTRL-C when it was done with mounting, then after a long time, when it tries to umount the mounts it gives the kernel panic.

regards,

Martin

_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs

maintainer
#9 lore raw
In reply to Martin Vogt
Quoted 26 lines · Martin Vogt
Quoted 12 lines · Martin Vogt
Quoted 4 lines · Ian Kent

You would need to enable debug logging.
autofs and syslog setup instructions for this can be seen at
http://people.redhat.com/jmoyer.

I think I can simply start it with "-d" ?.
As from the page this logging is meant to be used when the daemon ist started without debugging, but I can start it directly and can directly hang autofs.

Quoted 5 lines

Hm, I think I will write a small script for you, which lets you simply reproduce this behaviour.

(A script with 2000 direct bind mount :)

Hello list,

the following script:

#!/bin/sh
NET=/net/pxe1/var/tmp
for i in seq 1 2025 ; do

Quoted 8 lines
    echo "/homes/vogt${i} -fstype=bind,ro :${NET}"

done

creates a direct mount map with 2025 direct mount.
(I assume you know how to configure autofs how to use this map :) (Please really use a remote host for the mounts when you trigger it, for "localhost" you will find another bug, but currently I'm focused on the remote part, so really use a remote machine here)

What do you mean?

Are you saying that entries like "localhost:/net/pxe1/var/tmp", when /net/pxe1/var/tmp is local path are a problem or when the colon escaped path, /net/pxe1/var/tmp refers to another map for the host pxe1 that happens to be the localhost?

Quoted 24 lines

Then run a find . -maxdepth 2 to really trigger the mounts. These are the bugs:

- SuSE 11.1 rc1 hangs on the 1024th mount(autofs-5.0.3+patches)
- RHEL52 works (autofs-5.0.1-rc1) on mounting
- RHEL52 has a kernel panic on unmounting (see screenshot attachment)

(started with: automount -d -f -t 600 )

For the kernel panic I started automount in the forground and hit CTRL-C when it was done with mounting, then after a long time, when it tries to umount the mounts it gives the kernel panic.

regards,

Martin

_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs

maintainer
#10 lore raw
In reply to Martin Vogt
Quoted 16 lines · Martin Vogt
Quoted 15 lines · Martin Vogt
Quoted 4 lines · Ian Kent

You would need to enable debug logging.
autofs and syslog setup instructions for this can be seen at
http://people.redhat.com/jmoyer.

I think I can simply start it with "-d" ?.
As from the page this logging is meant to be used when the daemon ist started without debugging, but I can start it directly and can directly hang autofs.

Hm, I think I will write a small script for you, which lets you simply reproduce this behaviour.

Quoted 6 lines
Quoted 2 lines

(A script with 2000 direct bind mount :)

Hello list,

the following script:

There are a couple more problems with this as well.

Quoted 6 lines

#!/bin/sh
NET=/net/pxe1/var/tmp
for i in seq 1 2025 ; do

    echo "/homes/vogt${i} -fstype=bind,ro :${NET}"

done

There is no file system type "bind".

This possibly works because the ":" escape will cause autofs to attempt a bind mount and since the "-s" option is used for the mount the invalid options will be ignored.

Also, if /net/pxe1/var/tmp is mounted from remote host and the directories /net/pxe1/var/tmp/vogt${i} don't already exist mounts should fail but your example to duplicate the problem doesn't mention this at all. Come to think of it that is likely the case if this is local as well.

These comments may seem like I'm being picky but if we're to duplicate a problem then the setup "must" be completely specified so we both work with identical setups or we will end up going around in circles each with potentially different and inconsistent results.

Quoted 30 lines

creates a direct mount map with 2025 direct mount.
(I assume you know how to configure autofs how to use this map :) (Please really use a remote host for the mounts when you trigger it, for "localhost" you will find another bug, but currently I'm focused on the remote part, so really use a remote machine here)

Then run a find . -maxdepth 2 to really trigger the mounts. These are the bugs:

- SuSE 11.1 rc1 hangs on the 1024th mount(autofs-5.0.3+patches)
- RHEL52 works (autofs-5.0.1-rc1) on mounting
- RHEL52 has a kernel panic on unmounting (see screenshot attachment)

(started with: automount -d -f -t 600 )

For the kernel panic I started automount in the forground and hit CTRL-C when it was done with mounting, then after a long time, when it tries to umount the mounts it gives the kernel panic.

regards,

Martin

_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs