Skip to contentSkip to conversation

Difference in behaviour between 4.1.3 and 4.1.4

DISCUSSION Jeff Moyer 3 participants 3 messages Aug 2, 2005 – Aug 3, 2005 1 message not in the archive Kernel automounter

lore
Share & tools
lore

Jeff Moyer

author
#1 lore raw
In reply to a message not in the archive

==> Regarding [autofs] Difference in behaviour between 4.1.3 and 4.1.4; Max Matveev <[email protected]> adds:

makc> It seems that 4.1.4 has fixed a problem which 4.1.3 suffers from: if makc> a server does not export /, then autofs mount via auto.net would fail makc> with the following in the syslog:

makc> Aug 2 18:11:46 laura automount[6968]: mount(nfs): mkdir_path makc> /net/mazur/var failed: Operation not permitted

makc> This is with SLES9 and autofs4-4.1.3. FC4 with autofs-4.1.4-5 works. makc> Whould anybody know which particular change in 4.1.4 is responsible makc> for fixing that problem? And is it something which was changed from makc> 4.1.3 to 4.1.4 or is it FC's good work?

I have never seen this issue. I haven't seen it in the upstream autofs package nor in any variant of the Red Hat packages with which I work.

-Jeff

#2 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"jmoyer" == Jeff Moyer <[email protected]> writes:

jmoyer> ==> Regarding [autofs] Difference in behaviour between 4.1.3 and 4.1.4; Max Matveev <[email protected]> adds:
makc> It seems that 4.1.4 has fixed a problem which 4.1.3 suffers from: if
makc> a server does not export /, then autofs mount via auto.net would fail
makc> with the following in the syslog:

makc> Aug 2 18:11:46 laura automount[6968]: mount(nfs): mkdir_path makc> /net/mazur/var failed: Operation not permitted

makc> This is with SLES9 and autofs4-4.1.3. FC4 with autofs-4.1.4-5 works. makc> Whould anybody know which particular change in 4.1.4 is responsible makc> for fixing that problem? And is it something which was changed from makc> 4.1.3 to 4.1.4 or is it FC's good work?

jmoyer> I have never seen this issue. I haven't seen it in the jmoyer> upstream autofs package nor in any variant of the Red Hat jmoyer> packages with which I work.

Dang! I was hopeing it was a known issue and I wouldn't have to dive into the code - apparently 4.0.0-pre-something on Mandrake behave similarly. Maybe it's a kernel module issue, not the user-space automounter one.

max

#3 lore raw
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

"makc" == Max Matveev <[email protected]> writes:
"jmoyer" == Jeff Moyer <[email protected]> writes:

jmoyer> I have never seen this issue. I haven't seen it in the jmoyer> upstream autofs package nor in any variant of the Red Hat jmoyer> packages with which I work.

makc> Dang! I was hopeing it was a known issue and I wouldn't have to dive makc> into the code - apparently 4.0.0-pre-something on Mandrake behave makc> similarly. Maybe it's a kernel module issue, not the user-space makc> automounter one.

Scrap that - happened to be a mismatch between kernel and user space:
kernel at autofs3, userspace at autofs4, modprobe.conf got clobbered during update.

max