Skip to contentSkip to conversation

Low priority question: negative cache in autofs5

DISCUSSION Ondrej Valousek 2 participants 6 messages Dec 5, 2008 Kernel automounter

lore
Share & tools
lore
#0 lore raw

Probably to Ian:
I am just looking in the autofs5 (from RHEL5) source. I have an indirect nis map:
auto.master:
/appli auto.appli
/proj auto.proj

Now, auto.proj contains a wildcard entry (* nfsserver:/share/&) but auto.appli does not.

1. Every time I try to enter (shortly after each other) /proj/nonexistent_directory, I got this:

Dec  5 12:10:45 ara automount[3101]: rmdir_path: lstat of

/proj/nonexistent_directory failed
... why did not the negative cache save us the expensive call to lstat?

2. Every time I try to enter (shortly after each other) /appli/nonexistent_directory, I got this:

Dec  5 12:11:41 ara automount[3101]: lookup_mount: lookup(yp): key

"nonexistent" not found in map
... again, looks like the nis daemon was consulted but the negative cache should take the place.

Maybe I do not understand the concept of negative caching well.... Many thanks,

Ondrej

maintainer
#1 lore raw
Quoted 17 lines · Ondrej Valousek

Probably to Ian:
I am just looking in the autofs5 (from RHEL5) source. I have an indirect nis map:
auto.master:
/appli auto.appli
/proj auto.proj

Now, auto.proj contains a wildcard entry (* nfsserver:/share/&) but auto.appli does not.

1. Every time I try to enter (shortly after each other) /proj/nonexistent_directory, I got this:

Dec  5 12:10:45 ara automount[3101]: rmdir_path: lstat of

/proj/nonexistent_directory failed
... why did not the negative cache save us the expensive call to lstat?

Quoted 6 lines

2. Every time I try to enter (shortly after each other) /appli/nonexistent_directory, I got this:

Dec  5 12:11:41 ara automount[3101]: lookup_mount: lookup(yp): key

"nonexistent" not found in map
... again, looks like the nis daemon was consulted but the negative cache should take the place.

Known bug with v5 handling of negative caching of non-existent keys. I'm working on it but it is proving a little bit tricky because of possible multiple map sources listed in nsswitch.conf (at least that's where I'm currently at).

Quoted 2 lines

Maybe I do not understand the concept of negative caching well....

No .. you got it right .. I missed it.

Another thing, there are quite a few changes going into RHEL-5.3 autofs which will make their way into RHEL-4.8 in due course. Hopefully you will not get caught by them but it is worth logging calls for issues in case you are seeing a known issue.

Ian

#2 lore raw

Hi Ian,

Thanks for the quick reply. And what is the answer to the first question please (regarding lstat & wildcard entry)? :-)
It is not he same case I guess....
Many thanks,

Ondrej

Quoted 46 lines · Ian Kent
Quoted 17 lines · Ondrej Valousek

Probably to Ian:
I am just looking in the autofs5 (from RHEL5) source. I have an indirect nis map:
auto.master:
/appli auto.appli
/proj auto.proj

Now, auto.proj contains a wildcard entry (* nfsserver:/share/&) but auto.appli does not.

1. Every time I try to enter (shortly after each other) /proj/nonexistent_directory, I got this:

Dec  5 12:10:45 ara automount[3101]: rmdir_path: lstat of

/proj/nonexistent_directory failed
... why did not the negative cache save us the expensive call to lstat?

Quoted 7 lines

2. Every time I try to enter (shortly after each other) /appli/nonexistent_directory, I got this:

Dec  5 12:11:41 ara automount[3101]: lookup_mount: lookup(yp): key

"nonexistent" not found in map
... again, looks like the nis daemon was consulted but the negative cache should take the place.

Known bug with v5 handling of negative caching of non-existent keys. I'm working on it but it is proving a little bit tricky because of possible multiple map sources listed in nsswitch.conf (at least that's where I'm currently at).

Quoted 2 lines

Maybe I do not understand the concept of negative caching well....

No .. you got it right .. I missed it.

Another thing, there are quite a few changes going into RHEL-5.3 autofs which will make their way into RHEL-4.8 in due course. Hopefully you will not get caught by them but it is worth logging calls for issues in case you are seeing a known issue.

Ian

maintainer
#3 lore raw
Quoted 4 lines · Ondrej Valousek

Hi Ian,

Thanks for the quick reply. And what is the answer to the first question please (regarding lstat & wildcard entry)? :-)

The negative cache working properly will return a fail immediately so you shouldn't see this.

But then it shouldn't happen for the first case either. There are quite a few changes scheduled for the next update and I haven't seen this for a while now so it's a bit hard to get exited about it.

Quoted 53 lines

It is not he same case I guess....
Many thanks,

Ondrej

Quoted 46 lines · Ian Kent
Quoted 17 lines · Ondrej Valousek

Probably to Ian:
I am just looking in the autofs5 (from RHEL5) source. I have an indirect nis map:
auto.master:
/appli auto.appli
/proj auto.proj

Now, auto.proj contains a wildcard entry (* nfsserver:/share/&) but auto.appli does not.

1. Every time I try to enter (shortly after each other) /proj/nonexistent_directory, I got this:

Dec  5 12:10:45 ara automount[3101]: rmdir_path: lstat of

/proj/nonexistent_directory failed
... why did not the negative cache save us the expensive call to lstat?

Quoted 7 lines

2. Every time I try to enter (shortly after each other) /appli/nonexistent_directory, I got this:

Dec  5 12:11:41 ara automount[3101]: lookup_mount: lookup(yp): key

"nonexistent" not found in map
... again, looks like the nis daemon was consulted but the negative cache should take the place.

Known bug with v5 handling of negative caching of non-existent keys. I'm working on it but it is proving a little bit tricky because of possible multiple map sources listed in nsswitch.conf (at least that's where I'm currently at).

Quoted 2 lines

Maybe I do not understand the concept of negative caching well....

No .. you got it right .. I missed it.

Another thing, there are quite a few changes going into RHEL-5.3 autofs which will make their way into RHEL-4.8 in due course. Hopefully you will not get caught by them but it is worth logging calls for issues in case you are seeing a known issue.

Ian

#4 lore raw
Quoted 10 lines

The negative cache working properly will return a fail immediately so you shouldn't see this.

But then it shouldn't happen for the first case either. There are quite a few changes scheduled for the next update and I haven't seen this for a while now so it's a bit hard to get exited about it.

Ok, I understand - in summary:
#1 problem should go [hopefully] away with 5.3
#2 problem is known bug being worked on....
Thanks!
O.

maintainer
#5 lore raw
Quoted 9 lines · Ondrej Valousek
Quoted 9 lines

The negative cache working properly will return a fail immediately so you shouldn't see this.

But then it shouldn't happen for the first case either. There are quite a few changes scheduled for the next update and I haven't seen this for a while now so it's a bit hard to get exited about it.

Quoted 3 lines

Ok, I understand - in summary:
#1 problem should go [hopefully] away with 5.3
#2 problem is known bug being worked on....

Right, but problem #1 may be tied to problem #2, not quite sure yet. A fix for the negative cache issue is way too late for 5.3. We would need to get a test package to you for that, once it's done.

Quoted 2 lines

Thanks!
O.