All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Quenelle <chris.quenelle@Oracle.COM>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org, Frank Thommen <frank.thommen@embl.de>
Subject: Re: two /net paths to the same local mount?
Date: Thu, 15 Jul 2010 13:08:01 -0700	[thread overview]
Message-ID: <4C3F6AA1.2040409@oracle.com> (raw)
In-Reply-To: <1278903227.2930.18.camel@localhost>

I went through this thread and collected all the information
in a problem description.  I also included sysrq dump
output before and during the problem.  It's 300k.  I can
send it to the list in email if you prefer.  For now
it's available here:

http://quenelle.org/unix/wp-content/uploads/2010/07/linux-log.txt

Again, I want to thank you guys for your time.  I've learned a lot.

From the dump output I can see that there is one additional
"automount" thread when the problem is happening.  I think
the new one has the number 5603.  But that number seems to be
in the "father" column, not the "pid" column.  I'm not sure
what that means.

automount     S 0000555555686e00     0  5603      1                4054 (NOTLB)
ffff810366a07e88 0000000000000086 0000000005f5e100 000000000000000a
       ffff810417dc62d8 ffff810417dc6080 ffff810001033700 001082fb301a703a
       0000000000000653 0000000001037030
Call Trace: <ffffffff8014a06b>{enqueue_hrtimer+90} <ffffffff802ea159>{schedule_hrtimer+41}
       <ffffffff8014a5af>{hrtimer_nanosleep+130} <ffffffff8014a6a5>{sys_nanosleep+76}
       <ffffffff8010ae42>{system_call+126}

Anyway, the full dumps are included in the log I pointed at above.

--chris



Ian Kent wrote:
> On Fri, 2010-07-09 at 15:04 -0700, Chris Quenelle wrote:
>> Ian Kent wrote:
>>
>>> strace output is often not very useful.
>>>
>>> If you think there is some sort of deadlock going on get a sysreq-t dump
>>> to syslog. We still haven't seen a debug log?
>> I've had reports that my emails are being delayed when they go out to the list.
>> If anyone is following along and you'd like me to add you to my cc:
>> lines so you get the email directly, let me know, and I'll do that.
> 
> That's going to happen if you post to a subscribers only list without
> subscribing to it.
> 
>> I'm getting close to my limits of what this problem is worth to me.
> 
> And yet you haven't really provided the information requested?
> 
> I don't remember but did we get the distribution and autofs version your
> using?
> 
>> I suspect the two broken paths will get unwedged if I reboot the system.
>> But I'd love to know how to prevent it from happening again.
>>
>> I saw these lines in /var/log/messages:
>>
>>>>>>> Jun 29 09:04:46 carabas automount[11786]: Debug logging set for /net
>>>>>>> Jun 29 09:09:22 carabas automount[11786]: get_pkt: message pending on control fifo.
>>>>>>> Jun 29 09:09:22 carabas automount[11786]: Basic logging set for /net
>> Does that mean that all debugging output from automount should be
>> going to that file?  Or could the debug output still be going someplace
>> else (or into /dev/null?) In between the first line of that log output and
>> the last line, I provoked a correctly functioning automount of
>> a local file system, and I also tried to access the "broken" path
>> to the local filesystem.
> 
> What file, I don't understand what you mean?
> 
> But you don't mention what you have done to tell syslog to actually send
> "all" facility daemon messages to the syslog.
> 
> Try having a look at Jeffs page http://people.redhat.com/jmoyer for a
> description debug logging setup.
> 
>> So that in combination with strace/automount not giving any output
>> when I access the broken path, makes me think the control path
>> is not getting out of the kernel.
> 
> Maybe.
> 
>> Can you point me to an explanation of what a "sysreq-t dump" is and
>> how to get it?  I don't have access to the console of this machine,
>> hopefully it's something I can do from a root term window.
> 
> Wherever your distribution's has kernel documentation (or a package that
> contains the documentation) look at Documentation/sysrq.txt.
> 
> Often, you will find you can:
> 
> echo "t" > /proc/sysrq-trigger
> 
> to get a trace dump, which is what I'm asking for.
> 
>> To summarize my problem, I have a test set of paths to access a local
>> filesystem, 7 work and 2 don't.
>>
>> /net/carabas/export/home1
>> /net/carabas/export/home2    <-- fails
>> /net/carabas/export/home3    <-- fails
>> /net/carabas.sfbay/export/home1
>> /net/carabas.sfbay/export/home2
>> /net/carabas.sfbay/export/home3
>> /net/carabas.sfbay.sun.com/export/home1
>> /net/carabas.sfbay.sun.com/export/home2
>> /net/carabas.sfbay.sun.com/export/home3
>>
>>
>> I don't see anythign suspicious in the output of:
>> showmount
>> df
>> /etc/host.conf
>> strace automount
>> automount -l debug /net
>>
>>
>>
>>
>> --chris
> 
> 

  reply	other threads:[~2010-07-15 20:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21 19:17 two /net paths to the same local mount? Chris Quenelle
2010-06-22  2:05 ` Michael Loftis
2010-06-23 18:32   ` Chris Quenelle
2010-06-24  3:00     ` Ian Kent
2010-06-29 16:14       ` Chris Quenelle
2010-06-30 13:12         ` Ian Kent
2010-06-30 14:57           ` Chris Quenelle
2010-07-01  2:19             ` Ian Kent
2010-07-07  0:27               ` Chris Quenelle
2010-07-07  4:22                 ` Ian Kent
2010-07-09 22:04                   ` Chris Quenelle
2010-07-12  2:53                     ` Ian Kent
2010-07-15 20:08                       ` Chris Quenelle [this message]
2010-07-16  7:28                         ` Ian Kent
     [not found]                           ` <4C47428A.809@oracle.com>
2010-07-22  3:45                             ` Ian Kent
2010-07-23 21:22                               ` Chris Quenelle

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=4C3F6AA1.2040409@oracle.com \
    --to=chris.quenelle@oracle.com \
    --cc=autofs@linux.kernel.org \
    --cc=frank.thommen@embl.de \
    --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.