From: Ian Kent <raven@themaw.net>
To: Thomas Connell <tconnell@modwest.com>
Cc: autofs@linux.kernel.org
Subject: Re: Mountpoint string corruption in autofs5.0.3-3?
Date: Sun, 26 Apr 2009 11:47:54 +0800 [thread overview]
Message-ID: <20090426034752.GA3084@zeus.themaw.net> (raw)
In-Reply-To: <49F0F494.4030008@modwest.com>
On Thu, Apr 23, 2009 at 05:07:00PM -0600, Thomas Connell wrote:
> Hi;
>
> I'm having a problem that I've attempted to debug and google on my own, but have reached my limits of understanding. I'm hoping
> the list may be able to provide some insight.
>
> Some back story:
>
> I inherited this setup, which was discussed in this list, a little while ago:
> http://linux.kernel.org/pipermail/autofs/2009-February/005575.html
>
> As that link provided, I was able to backport debian 5.0 autofs5 to debian 4.0 with the little patch. My testing seemed to
> indicate it was working fine.
>
> When I started to roll it out, the automounter process started working the CPU really hard, and some automounts that were
> mounting before were not.
>
>
> Here are the verbose logs from when the first access attempts to hit the mountpoint. I apologize for not obscuring the domain
> name that is also the mount point, but since that is what is corrupted, I don't see a way not to post it:
>
>
> Apr 23 14:27:21 web6 automount[31779]: handle_packet: type = 3
> Apr 23 14:27:21 web6 automount[31779]: handle_packet_missing_indirect: token 5106, name federalhousingtaxcredit.com, request pid
> 14419
> Apr 23 14:27:21 web6 automount[31779]: attempting to mount entry /domains/f/federalhousingtaxcredit.com
> Apr 23 14:27:21 web6 automount[31779]: lookup_mount: lookup(ldap): looking up federalhousingtaxcredit.com
> Apr 23 14:27:21 web6 automount[31779]: do_bind: lookup(ldap): ldap anonymous bind returned 0
> Apr 23 14:27:21 web6 automount[31779]: lookup_one: lookup(ldap): searching for
> "(&(objectclass=automount)(|(cn=federalhousingtaxcredit.com)(cn=/)(cn=\2A)))" under
> "ou=domains,ou=jails,ou=Mounts,dc=modwest,dc=com"
> Apr 23 14:27:22 web6 automount[31779]: lookup_one: lookup(ldap): getting first entry for cn="federalhousingtaxcredit.com"
> Apr 23 14:27:22 web6 automount[31779]: lookup_one: lookup(ldap): examining first entry
> Apr 23 14:27:22 web6 automount[31779]: lookup_one: lookup(ldap): examining first entry
> Apr 23 14:27:22 web6 automount[31779]: lookup_mount: lookup(ldap): federalhousingtaxcredit.com -> /
> :/www/vhosts/f/federalhousingtaxcredit.com /.renv :/mnt/jail
> Apr 23 14:27:22 web6 automount[31779]: parse_mount: parse(sun): expanded entry: / :/www/vhosts/f/federalhousingtaxcredit.com
> /.renv :/mnt/jail
> Apr 23 14:27:22 web6 automount[31779]: parse_mount: parse(sun): gathered options: vd,strict
> Apr 23 14:27:22 web6 automount[31779]: parse_mount: parse(sun): dequote("/") -> /
> Apr 23 14:27:22 web6 automount[31779]: parse_mapent: parse(sun): gathered options: vd,strict
> Apr 23 14:27:22 web6 automount[31779]: parse_mapent: parse(sun): dequote(":/www/vhosts/f/federalhousingtaxcredit.com") ->
> :/www/vhosts/f/federalhousingtaxcredit.com
> Apr 23 14:27:22 web6 automount[31779]: add_offset_entry: parse(sun): added multi-mount offset / -> -vd,strict
> :/www/vhosts/f/federalhousingtaxcredit.com
> Apr 23 14:27:22 web6 automount[31779]: parse_mount: parse(sun): dequote("/.renv") -> /.renv
> Apr 23 14:27:22 web6 automount[31779]: parse_mapent: parse(sun): gathered options: vd,strict
> Apr 23 14:27:22 web6 automount[31779]: parse_mapent: parse(sun): dequote(":/mnt/jail") -> :/mnt/jail
> Apr 23 14:27:22 web6 automount[31779]: add_offset_entry: parse(sun): added multi-mount offset /.renv -> -vd,strict :/mnt/jail
> Apr 23 14:27:22 web6 automount[31779]: parse_mapent: parse(sun): gathered options: vd,strict
> Apr 23 14:27:22 web6 automount[31779]: parse_mapent: parse(sun): dequote(":/www/vhosts/f/federalhousingtaxcredit.com") ->
> :/www/vhosts/f/federalhousingtaxcredit.com
> Apr 23 14:27:22 web6 automount[31779]: sun_mount: parse(sun): mounting root /domains/f/federalhousingtaxcredit.com, mountpoint
> /, what :/www/vhosts/f/federalhousingtaxcredit.com, fstype nfs, options vd
> Apr 23 14:27:22 web6 automount[31779]: mount_mount: mount(nfs): root=/domains/f/federalhousingtaxcredit.com name=/
> what=:/www/vhosts/f/federalhousingtaxcredit.com, fstype=nfs, options=vd
> Apr 23 14:27:22 web6 automount[31779]: mount_mount: mount(nfs): nfs options="vd", nosymlink=0, ro=0
> Apr 23 14:27:22 web6 automount[31779]: mount_mount: mount(nfs): calling mkdir_path /domains/f/federalhousingtaxcredit.com
> Apr 23 14:27:22 web6 automount[31779]: mount_mount: mount(nfs): / is local, attempt bind mount
> Apr 23 14:27:22 web6 automount[31779]: mount_mount: mount(bind): calling mkdir_path /domains/f/federalhousingtaxcred���om
> Apr 23 14:27:22 web6 automount[31779]: mount_mount: mount(bind): calling mount --bind -s -o defaults
> /www/vhosts/f/federalhousingtaxcredit.com /domains/f/federalhousingtaxcred���
> Apr 23 14:27:22 web6 automount[31779]: >> mount: mount point /domains/f/federalhousingtaxcred��� does not exist
Is this string corruption really present in the log?
I can't see how that corruption can occur looking at the code.
If this really is in the log so you will need to narrow down where this
corruption is happening.
Adding a debug logging patch to the Debian build to log what is received
by modules/mount_bind.c:mount_mount() would be the first thing to do. A
debug log statement similar to the one at the top of
modules/mount_nfs.c:mount_mount() would be enough to tell if this happens
before the call to perform bind mount, or after.
Ian
_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs
next prev parent reply other threads:[~2009-04-26 3:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 23:07 Mountpoint string corruption in autofs5.0.3-3? Thomas Connell
2009-04-26 3:47 ` Ian Kent [this message]
2009-04-26 16:36 ` Thomas Connell
2009-04-28 4:52 ` 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=20090426034752.GA3084@zeus.themaw.net \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=tconnell@modwest.com \
/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.