All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Ondrej Valousek <webserv@s3group.cz>
Cc: "autofs@linux.kernel.org" <autofs@linux.kernel.org>
Subject: Re: Autofs Negative cache
Date: Mon, 14 Sep 2009 17:03:19 +0800	[thread overview]
Message-ID: <4AAE06D7.3090703@themaw.net> (raw)
In-Reply-To: <4AADEE87.3040609@s3group.cz>

Ondrej Valousek wrote:
> Hi Ian,
> 
> Can we expect someday autofs in RHEL-5 to have a working negative cache?
> Seems like it still does not work in the last update (5.4):

You'll need to be a bit more specific about what is wrong.

What is your impression of what is actually happening below?

Be aware that the negative caching cannot be done in the 2.6 kernel
module so we will always get lookups coming to the daemon. Also, some
things such as "cd" always cause multiple call backs so we will see
multiple requests although the actual map lookup and mount attempt
should be eliminated. Are you saying that maybe I'm checking too late
during the call back?

> 
> Sep 14 09:14:57 dorado_v1 automount[16281]:
> handle_packet_missing_indirect: token 132, name test, request pid 16183
> Sep 14 09:14:57 dorado_v1 automount[16281]: attempting to mount entry
> /proj/test
> Sep 14 09:14:57 dorado_v1 automount[16281]: file map not found
> Sep 14 09:14:57 dorado_v1 automount[16281]: lookup_mount: lookup(yp):
> looking up test
> Sep 14 09:14:57 dorado_v1 automount[16281]: ioctl_send_fail: token = 132
> Sep 14 09:14:57 dorado_v1 automount[16281]: failed to mount /proj/test
> Sep 14 09:14:58 dorado_v1 automount[16281]: handle_packet: type = 3
> Sep 14 09:14:58 dorado_v1 automount[16281]:
> handle_packet_missing_indirect: token 133, name test, request pid 16183
> Sep 14 09:14:58 dorado_v1 automount[16281]: attempting to mount entry
> /proj/test
> Sep 14 09:14:58 dorado_v1 automount[16281]: file map not found
> Sep 14 09:14:58 dorado_v1 automount[16281]: lookup_mount: lookup(yp):
> looking up test
> Sep 14 09:14:58 dorado_v1 automount[16281]: ioctl_send_fail: token = 133
> Sep 14 09:14:58 dorado_v1 automount[16281]: handle_packet: type = 3
> Sep 14 09:14:58 dorado_v1 automount[16281]:
> handle_packet_missing_indirect: token 134, name test, request pid 16183
> Sep 14 09:14:58 dorado_v1 automount[16281]: failed to mount /proj/test
> Sep 14 09:14:58 dorado_v1 automount[16281]: attempting to mount entry
> /proj/test
> Sep 14 09:14:58 dorado_v1 automount[16281]: file map not found
> Sep 14 09:14:58 dorado_v1 automount[16281]: lookup_mount: lookup(yp):
> looking up test
> Sep 14 09:14:58 dorado_v1 automount[16281]: ioctl_send_fail: token = 134
> Sep 14 09:14:58 dorado_v1 automount[16281]: failed to mount /proj/test
> Sep 14 09:14:58 dorado_v1 automount[16281]: handle_packet: type = 3
> Sep 14 09:14:58 dorado_v1 automount[16281]:
> handle_packet_missing_indirect: token 135, name test, request pid 16183
> 
> Thanks,
> Ondrej
> 
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs

  reply	other threads:[~2009-09-14  9:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14  7:19 Autofs Negative cache Ondrej Valousek
2009-09-14  9:03 ` Ian Kent [this message]
2009-09-14  9:45   ` Ondrej Valousek

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=4AAE06D7.3090703@themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=webserv@s3group.cz \
    /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.