From: Farkas Levente <lfarkas@bppiac.hu>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: automount never umount
Date: Wed, 23 Nov 2005 14:18:20 +0100 [thread overview]
Message-ID: <43846C1C.3050305@bppiac.hu> (raw)
In-Reply-To: <Pine.LNX.4.63.0511232105320.3200@donald.themaw.net>
Ian Kent wrote:
> On Wed, 23 Nov 2005, Farkas Levente wrote:
>>Jeff Moyer wrote:
>>output of dmesg or /var/log/daemon? there is nothing in dmesg.
>>i'm running this kernel currently and mount nfs and smbfs servers.
>>---------------------------
>>root 1974 0.0 0.0 1788 736 ? Ss 10:05 0:00
>>/usr/sbin/automount --timeout=60 --debug /smb program /etc/auto.smb
>>root 1976 0.0 0.0 1788 736 ? Ss 10:05 0:00
>>/usr/sbin/automount --timeout=60 --debug /net program /etc/auto.net
>>---------------------------
>>how long should i wait? as the timeout is 1 minute, they should have to
>>be umounted, but not. here is the relevant part of daemon log which
>>don't tell me too much:-(
>
>
> You've waited long enough. Your timeout was 60 seconds.
>
> This is really strange. We didn't catch any activity from the patch so I
> don't know why it isn't expiring. Come to think of it we we should have
> at least got some kernel messages?
>
> What version was the kernel you originally saw this on?
# rpm -q kernel
kernel-2.6.14-1.1637_FC4
kernel-2.6.14-1.1641_FC4.jmoyertest.1
> Jeff, I'm wondering if this is a regression from the latest patch.
> Was that in the above kernel?
>
> Farkas, if your willing the next step in this process is likely to
> generate even more output but hopefully will give us more info.
what should i do?
--
Levente "Si vis pacem para bellum!"
next prev parent reply other threads:[~2005-11-23 13:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 15:31 automount never umount Farkas Levente
2005-11-22 13:27 ` Ian Kent
2005-11-22 9:43 ` Farkas Levente
2005-11-22 13:03 ` Ian Kent
2005-11-22 16:19 ` Farkas Levente
2005-11-22 16:50 ` Jeff Moyer
2005-11-22 21:24 ` Farkas Levente
2005-11-22 23:27 ` Ian Kent
2005-11-23 0:24 ` Jeff Moyer
2005-11-23 9:27 ` Farkas Levente
2005-11-23 13:13 ` Ian Kent
2005-11-23 13:18 ` Farkas Levente [this message]
2005-11-23 15:28 ` Jeff Moyer
2005-11-23 15:38 ` Ian Kent
2005-11-23 16:57 ` Jeff Moyer
2005-11-23 17:13 ` Farkas Levente
2005-11-23 17:16 ` Jeff Moyer
2005-11-24 10:05 ` Farkas Levente
2005-11-24 12:10 ` Ian Kent
2005-11-24 23:17 ` Farkas Levente
2005-11-28 15:41 ` Jeff Moyer
2005-11-28 16:11 ` Ian Kent
2005-11-29 12:28 ` Farkas Levente
2005-12-01 9:31 ` Farkas Levente
2005-12-01 11:03 ` Ian Kent
2005-12-01 11:36 ` Farkas Levente
2005-12-01 12:57 ` Jeff Moyer
2005-12-01 13:41 ` Farkas Levente
2005-12-01 15:02 ` Ian Kent
2005-12-01 13:45 ` Ian Kent
2005-12-01 13:53 ` Farkas Levente
2005-12-01 15:04 ` Ian Kent
2005-11-23 14:26 ` Ian Kent
2005-11-22 23:18 ` Ian Kent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43846C1C.3050305@bppiac.hu \
--to=lfarkas@bppiac.hu \
--cc=autofs@linux.kernel.org \
--cc=raven@themaw.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.