Skip to contentSkip to conversation

Strange autofs V4.0 problems

DISCUSSION Alan.Burke 5 participants 7 messages Feb 2, 2004 – Feb 3, 2004 Kernel automounter

lore
Share & tools
lore

Alan.Burke

author
#0 lore raw

Hi Folks,

We're having a strange problem with autofs V4.1 on RH8. I hope someone can help.

Can't connect to certain Network Appliances boxes. No rhyme or reason. Both /net and /home directories fail on some Net Apps but not others. The Net App boxes are exporting correctly. We can mount the netapps, just not via autofs.

Errors from the messages file...

Jan 29 15:36:54 cfl27 automount[19457]: mount(nfs): nfs: mount failure 820ntap:/vol/vol1 on /net/820ntap/vol/vol1
Jan 29 15:36:54 cfl27 automount[19457]: failed to mount /net/820ntap
Jan 29 15:36:54 cfl27 automount[19467]: >> mount: 820ntap:/vol/vol1 failed, reason given by server: Permission denied

Any Ideas?

Thanks in advance,

alan

Signature · 2 lines
Alan J. Burke		Engineering IS Manager
Analog Devices		Email: [email protected]
#1 lore raw
Quoted 10 lines · Alan.Burke

Can't connect to certain Network Appliances boxes. No rhyme or reason. Both /net and /home directories fail on some Net Apps but not others. The Net App boxes are exporting correctly. We can mount the netapps, just not via autofs.

Errors from the messages file...

Jan 29 15:36:54 cfl27 automount[19457]: mount(nfs): nfs: mount failure 820ntap:/vol/vol1 on /net/820ntap/vol/vol1
Jan 29 15:36:54 cfl27 automount[19457]: failed to mount /net/820ntap
Jan 29 15:36:54 cfl27 automount[19467]: >> mount: 820ntap:/vol/vol1 failed, reason given by server: Permission denied

The fact that you're seeing that in your logs shows that autofs is working fine.. your host tried to mount the directory and was denied by the server. I'm seeing the exact same thing for some new linux boxes I just installed over the weekend and some of our NetApp filers, and we're seeing the same thing from some new Solaris hosts as well.

I'm wondering if there's some kind of name/ip caching bug on the netapps that caches a deny for a very long period if you try to mount before your netgroups/dns is updated with the new host information.

Signature · 3 lines
Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com
Drew: "Violence doesn't solve anything? World War I. World War II. Star Wars.
every Super Bowl. Who says violence doesn't solve anything?!" ==> Drew Cary Show
#2 lore raw
Quoted 4 lines · Mike Marion

The fact that you're seeing that in your logs shows that autofs is working fine.. your host tried to mount the directory and was denied by the server. I'm seeing the exact same thing for some new linux boxes I just installed over the weekend and some of our NetApp filers, and we're seeing the same thing from some new Solaris hosts as well.

I'm wondering if there's some kind of name/ip caching bug on the netapps that caches a deny for a very long period if you try to mount before your netgroups/dns is updated with the new host information.

If you can mount them by hand on the same box not using autofs, then it seems more likely to be an autofs issue.

Michael

#3 lore raw
Quoted 2 lines · Michael Blandford

If you can mount them by hand on the same box not using autofs, then it seems more likely to be an autofs issue.

Tried that.. can't. Going to have our netapp people look into it as other netaps are fine.

Signature · 7 lines
Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com
Lisa: "As you know, we've been swimming. And we've developed a taste for it. We
agree that getting our own pool is the way to go. Now before you respond, you 
should know that your refusal will result in months and months of..."
Bart, Lisa: "CanwehaveapoolDad? CanwehaveapoolDad? CanwehaveapoolDad? 
CanwehaveapoolDad? CanwehaveapoolDad?"
Homer: "I understand. Let us celebrate our agreement with the adding of chocolate to milk." -- Simpsons
#5 lore raw
In reply to Michael Blandford

use the 'nonstrict' opition in your auto.net script.

Quoted 18 lines · Michael Blandford
Quoted 4 lines · Mike Marion

The fact that you're seeing that in your logs shows that autofs is working fine.. your host tried to mount the directory and was denied by the server. I'm seeing the exact same thing for some new linux boxes I just installed over the weekend and some of our NetApp filers, and we're seeing the same thing from some new Solaris hosts as well.

I'm wondering if there's some kind of name/ip caching bug on the netapps that caches a deny for a very long period if you try to mount before your netgroups/dns is updated with the new host information.

If you can mount them by hand on the same box not using autofs, then it seems more likely to be an autofs issue.

Michael

_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs

Signature · 7 lines
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Rhythm & Hues
5404 Jandy Place
Los Angeles, CA 90066
Voice: 310 448-7763
Fax:   310 448-7600
[email protected]
#6 lore raw

Greg,

This worked immediately. Thank you for your help.

Annie

Quoted 26 lines · Greg Bradner

use the 'nonstrict' opition in your auto.net script.

Quoted 19 lines · Michael Blandford
Quoted 4 lines · Mike Marion

The fact that you're seeing that in your logs shows that autofs is working fine.. your host tried to mount the directory and was denied by the server. I'm seeing the exact same thing for some new linux boxes I just installed over the weekend and some of our NetApp filers, and we're seeing the same thing from some new Solaris hosts as well.

I'm wondering if there's some kind of name/ip caching bug on the netapps that caches a deny for a very long period if you try to mount before your netgroups/dns is updated with the new host information.

If you can mount them by hand on the same box not using autofs, then it seems more likely to be an autofs issue.

Michael

_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs

#4 lore raw
In reply to [email protected]
Quoted 6 lines · On 2 Feb, To: [email protected] wrote:
Quoted 2 lines

If you can mount them by hand on the same box not using autofs, then it seems more likely to be an autofs issue.

Tried that.. can't. Going to have our netapp people look into it as other netaps are fine.

We finally figured out that our netgroup.byname map was being truncated... and that's why smoe hosts weren't mounting when others could.

We added a ton of entries into our duty system, that expand out to netgroups on each host, so we went beyond the length a single entry can have. They're working on truncating the lists into sub-netgroups like we had to do years ago for some of the other netgroup maps.

Signature · 4 lines
Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com
"Administering a Linux server is no more difficult than properly running
Windows NT."
  -- Infoworld, November 24, 1997