5.0.0_beta1: does not auto-unmount
Hi Ian,
I run automount like this:
# automount -f -s -v --timeout 15 /.local/var/service/automount/master.file
My master.file is one-liner:
/mnt/auto program:/.local/var/service/automount/mapper.sh
mapper.sh is attached.
This setup (with this exact mapper.sh) worked flawlessly with 4.1.4, but with 5.0.0_beta1 I have a problem:
# automount -f -s -v --timeout 15 /.local/var/service/automount/master Starting automounter version 5.0.0_beta1, master map /.local/var/service/automount/master using kernel protocol version 5.00 using timeout 15 seconds; freq 4 secs
I do "cd /mnt/auto/vfat.sdb1" (sdb1 is my USB memory stick) and automount says:
attempting to mount entry /.local/mnt/auto/vfat.sdb1 mounted /mnt/auto/vfat.sdb1
So far so good, mount shows:/dev/sdb1 on /mnt/auto/vfat.sdb1 type vfat (rw,nosuid,noexec,fmask=0000,dmask=0000,codepage=cp866,iocharset=koi8-r,shortname=win95,quiet,uni_xlate)
But it never auto-unmounts. I am 100% sure nothing
is keeping files or directories busy on /dev/sdb1 (I cd'ed away from the directory). Automount is not saying anything, strace -p <PID> shows one line:
rt_sigtimedwait(~[CHLD CONT RTMIN RT_1],
I killed 4 hours of my time making automount 5.0.0 even start on my machine, and it's 4:00 am here, so at this time I am a rather unhappy panda and probably I'll go back to 4.1.4 instead of chasing down yet another bug.
# size autofs*/sbin/* text data bss dec hex filename 35143 916 10084 46143 b43f autofs-4.1.4_beta1/sbin/automount 118494 1344 884 120722 1d792 autofs-5.0.0_beta1/sbin/automount
During 4.1.4 -> 5.0.0 size has *tripled*. Uncool. :( --
vda
_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs
Ian Kent
maintainerQuoted 26 lines · Denys Vlasenko
Hi Ian,
I run automount like this:
# automount -f -s -v --timeout 15 /.local/var/service/automount/master.fileMy master.file is one-liner:
/mnt/autoprogram:/.local/var/service/automount/mapper.sh
mapper.shis attached.This setup (with this exact
mapper.sh) worked flawlessly with 4.1.4, but with 5.0.0_beta1 I have a problem:# automount -f -s -v --timeout 15 /.local/var/service/automount/master Starting automounter version 5.0.0_beta1, master map /.local/var/service/automount/master using kernel protocol version 5.00 using timeout 15 seconds; freq 4 secsI do "cd
/mnt/auto/vfat.sdb1" (sdb1 is my USB memory stick) and automount says:attempting to mount entry /.local/mnt/auto/vfat.sdb1 mounted
/mnt/auto/vfat.sdb1
Quoted 7 lines
So far so good, mount shows:
/dev/sdb1on/mnt/auto/vfat.sdb1type vfat (rw,nosuid,noexec,fmask=0000,dmask=0000,codepage=cp866,iocharset=koi8-r,shortname=win95,quiet,uni_xlate)But it never auto-unmounts. I am 100% sure nothing
is keeping files or directories busy on/dev/sdb1(I cd'ed away from the directory). Automount is not saying anything, strace -p <PID> shows one line:
Strange, I'll try and duplicate this and see how far I get. If you do want to make sure nothing is asking it to remount enable debug and ensure facility daemon.* is being logged. If there are accesses keeping it open the requesting pid will be logged.
Quoted 6 lines
rt_sigtimedwait(~[CHLD CONT RTMIN
RT_1],I killed 4 hours of my time making automount 5.0.0 even start on my machine, and it's 4:00 am here, so at this time I am a rather unhappy panda and probably I'll go back to 4.1.4 instead of chasing down yet another bug.
Ya but I'm getting there.
The change is huge to be sure, and many things do work well.
Quoted 7 lines
# size autofs*/sbin/* text data bss dec hex filename 35143 916 10084 46143 b43f autofs-4.1.4_beta1/sbin/automount 118494 1344 884 120722 1d792 autofs-5.0.0_beta1/sbin/automountDuring 4.1.4 -> 5.0.0 size has *tripled*. Uncool. :(
Not sure what I can do about that, sorry.
Ian Kent
maintainerDenys,
On another note.
5.0.0_beta1?
Since beta1 there were five other beta and three rc releases. The initial release was actually 5.0.1 and were at 5.0.2 now with a bunch of corrections which need to be consolidated into 5.0.3 time soon. There have been many corrections including ones for expire issues.
Ian
Quoted 5 lines · Ian Kent
Denys,
On another note.
5.0.0_beta1?
It's the latest thing I found at
http://www.kernel.org/pub/linux/daemons/autofs/v4/
Aha. I see. I had to fetch stuff from
http://www.kernel.org/pub/linux/daemons/autofs/v5/
right?
--
vda
Ian Kent
maintainerQuoted 9 lines · Denys Vlasenko
Quoted 5 lines · Ian Kent
Denys,
On another note.
5.0.0_beta1?It's the latest thing I found at
Quoted 7 lines
http://www.kernel.org/pub/linux/daemons/autofs/v4/
Aha. I see. I had to fetch stuff from
http://www.kernel.org/pub/linux/daemons/autofs/v5/
right?
Yep, that's the place.
Ian
Quoted 12 lines · Ian Kent
Quoted 11 lines · Denys Vlasenko
Quoted 5 lines · Ian Kent
Denys,
On another note.
5.0.0_beta1?It's the latest thing I found at
Quoted 8 lines
Quoted 5 lines
Aha. I see. I had to fetch stuff from
http://www.kernel.org/pub/linux/daemons/autofs/v5/
right?
Yep, that's the place.
Ian
autofs-5.0.2 still references www.kernel.org/pub/linux/daemons/autofs/v4/:
# grep -r /v4 . ./INSTALL: from http://www.kernel.org/pub/linux/daemons/autofs/v4. ./autofs.spec:Source: ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/autofs-%{version}.tar.gz ./gentoo/net-fs/autofs/autofs-5.0.2.ebuild:SRC_URI_BASE="mirror://kernel/linux/daemons/${PN}/v4"
What do you think about removing autofs-5.0.0_beta1.tar.* from .../v4 directory in order to prevent confusion?
--
vda
Ian Kent
maintainerQuoted 22 lines · Denys Vlasenko
Quoted 12 lines · Ian Kent
Quoted 11 lines · Denys Vlasenko
Quoted 5 lines · Ian Kent
Denys,
On another note.
5.0.0_beta1?It's the latest thing I found at
Quoted 8 lines
Quoted 5 lines
Aha. I see. I had to fetch stuff from
http://www.kernel.org/pub/linux/daemons/autofs/v5/
right?
Yep, that's the place.
Ian
Quoted 6 lines
autofs-5.0.2 still references www.kernel.org/pub/linux/daemons/autofs/v4/:
# grep -r /v4 . ./INSTALL: from http://www.kernel.org/pub/linux/daemons/autofs/v4. ./autofs.spec:Source: ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/autofs-%{version}.tar.gz ./gentoo/net-fs/autofs/autofs-5.0.2.ebuild:SRC_URI_BASE="mirror://kernel/linux/daemons/${PN}/v4"
Ha, missed that completely.
Thnks.
Quoted 3 lines
What do you think about removing autofs-5.0.0_beta1.tar.* from .../v4 directory in order to prevent confusion?
Yes, I'd like to but I was a bit concerned that distros that pull these tarballs might expect them to be present.
Maybe I could encourage an update if I did, which would be desirable.
Ian
Quoted 11 lines
Quoted 6 lines
autofs-5.0.2 still references www.kernel.org/pub/linux/daemons/autofs/v4/:
# grep -r /v4 . ./INSTALL: from http://www.kernel.org/pub/linux/daemons/autofs/v4. ./autofs.spec:Source: ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/autofs-%{version}.tar.gz ./gentoo/net-fs/autofs/autofs-5.0.2.ebuild:SRC_URI_BASE="mirror://kernel/linux/daemons/${PN}/v4"Ha, missed that completely.
Thnks.Quoted 1 line
Quoted 7 lines
Quoted 2 lines
What do you think about removing autofs-5.0.0_beta1.tar.* from .../v4 directory in order to prevent confusion?
Yes, I'd like to but I was a bit concerned that distros that pull these tarballs might expect them to be present.
Maybe I could encourage an update if I did, which would be desirable.
I mean, by removing 5.0.0beta from v4 directory you will avoid having confused users thinking that 5.0.0_beta1 is latest.
I tried 5.0.2 today, summary:
-s --stderr missing
-f --foreground works, not mentioned in help text
I didn't go further, can't say whether it works for me. Will test 5.0.3 whenever you want.
--
vda
Ian Kent
maintainerQuoted 14 lines · Denys Vlasenko
Quoted 14 lines
Quoted 6 lines
autofs-5.0.2 still references www.kernel.org/pub/linux/daemons/autofs/v4/:
# grep -r /v4 . ./INSTALL: from http://www.kernel.org/pub/linux/daemons/autofs/v4. ./autofs.spec:Source: ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/autofs-%{version}.tar.gz ./gentoo/net-fs/autofs/autofs-5.0.2.ebuild:SRC_URI_BASE="mirror://kernel/linux/daemons/${PN}/v4"Ha, missed that completely.
Thnks.Quoted 3 lines
What do you think about removing autofs-5.0.0_beta1.tar.* from .../v4 directory in order to prevent confusion?
Quoted 7 lines
Quoted 4 lines
Yes, I'd like to but I was a bit concerned that distros that pull these tarballs might expect them to be present.
Maybe I could encourage an update if I did, which would be desirable.
I mean, by removing 5.0.0beta from v4 directory you will avoid having confused users thinking that 5.0.0_beta1 is latest.
Yes, I think I will remove all the v5 specific stuff from the v4 directory at the same time I post 5.0.3.
It's been quite a while and people that have version 5 should be aware of updates and really should be using later versions.
Review
Quoted 5 lines
I tried 5.0.2 today, summary:
(quoted diff) +0
-2-s --stderr missing -f --foreground works, not mentioned in help text
Are you sure you applied the additional foreground logging patch (well actually if you test 5.0.2 you should really apply all the patches listed in patch_order-5.0.2 to get a "current state" view).
Are you the same person that originally contributed these patches? I have the name "Denis Vlasenko" in the original patch emails.
Anyway, I never quite completely apply the patches but what we have now is fairly close. In particular I haven't provided a distinct "log to stderr". Over the considerable time this has been present I've rarely needed to use the foreground option but when I have I've always wanted to send the log to my tty. Especially since you can just redirect the output if you need to when running in foreground.
Ian
Quoted 8 lines · Ian Kent
Review
Quoted 4 lines
I tried 5.0.2 today, summary:
(quoted diff) +0
-2-s --stderr missing -f --foreground works, not mentioned in help textAre you sure you applied the additional foreground logging patch (well actually if you test 5.0.2 you should really apply all the patches listed in patch_order-5.0.2 to get a "current state" view).
Hmmm... no.
Quoted 2 lines
Are you the same person that originally contributed these patches? I have the name "Denis Vlasenko" in the original patch emails.
Yes. "Denys" is my country's officialdom's idea how to transliterate my name into Latin letters. [idiots]
Quoted 6 lines
Anyway, I never quite completely apply the patches but what we have now is fairly close. In particular I haven't provided a distinct "log to stderr". Over the considerable time this has been present I've rarely needed to use the foreground option but when I have I've always wanted to send the log to my tty. Especially since you can just redirect the output if you need to when running in foreground.
I don't understand you. Currently, even it --foreground mode automount logs everything to syslog, IIRC.
Hot do you redirect that? To where?
I want to be able to direct log to be on stderr or stdout (I log each daemon's output separately by capturing those). --
vda
Ian Kent
maintainerQuoted 10 lines · Denys Vlasenko
Quoted 8 lines · Ian Kent
Review
Quoted 4 lines
I tried 5.0.2 today, summary:
(quoted diff) +0
-2-s --stderr missing -f --foreground works, not mentioned in help textAre you sure you applied the additional foreground logging patch (well actually if you test 5.0.2 you should really apply all the patches listed in patch_order-5.0.2 to get a "current state" view).
Quoted 7 lines
Hmmm... no.
Quoted 2 lines
Are you the same person that originally contributed these patches? I have the name "Denis Vlasenko" in the original patch emails.
Yes. "Denys" is my country's officialdom's idea how to transliterate my name into Latin letters. [idiots]
HaHaha, right.
Quoted 11 lines
Quoted 7 lines
Anyway, I never quite completely apply the patches but what we have now is fairly close. In particular I haven't provided a distinct "log to stderr". Over the considerable time this has been present I've rarely needed to use the foreground option but when I have I've always wanted to send the log to my tty. Especially since you can just redirect the output if you need to when running in foreground.
I don't understand you. Currently, even it --foreground mode automount logs everything to syslog, IIRC.
Hot do you redirect that? To where?
The recent patch for foreground logging will send everything to stderr unconditionally. I should have realized you wouldn't get this bit, sorry.
Quoted 3 lines
I want to be able to direct log to be on stderr or stdout (I log each daemon's output separately by capturing those).
Yep, got it.
Hopefully the patch I mentioned above will do what's needed.
Ian