Skip to contentSkip to conversation

ENOENT on first reference to an automounted file

DISCUSSION Greg Earle 2 participants 2 messages Nov 17, 2007 – Nov 18, 2007 1 message not in the archive Kernel automounter

lore
Share & tools
lore

Greg Earle

author
#1 lore raw
In reply to a message not in the archive
Quoted 6 lines · Dan Halbert
Quoted 5 lines · Greg Earle

We use NIS for our maps, but just for fun, I decided to test turning "--ghost" *on* (we default to it off, and we also use "-nobrowse" on our Suns, so we like to keep them consistent), and ...

Quoted 6 lines

Greg, try the latest kernel, 2.6.9-55.0.12, which is now available from
RedHat and has also gone downstream to various other RH-source-based distributions. This works for us. I agree your ghost/non-ghost differences are odd and do not match my experience. But I see differences also based on client load.

I see that Red Hat just announced/released RHEL 4 Update 6 yesterday:

https://www.redhat.com/archives/nahant-list/2007-November/msg00068.html

It appears that this includes kernel 2.6.9-67. Can I safely assume that this new release quashes this pesky ENOENT bug once and for all?

More interestingly/importantly, RHEL 4 Update 6 includes autofs5 as a "Technology Preview". How does the autofs5 code in this new release compare with the mainline code in RHEL 5 Update 1, and is it considered robust enough to use in a production environment that depends heavily (as in, "life or death" - we use the automounter for *everything*) on automounting?

We started our RHEL 4 Update 5 upgrade cycle a month and a half ago but were stopped dead in our tracks by this bug.

Now that we have a workaround ("--ghost"), we are planning on pushing ahead, but I need to know whether I should try recommending that we instead move to Update 6 rather than continue to use Update 5 with a Band-Aid.

Thanks,

- Greg

maintainer
#2 lore raw
Quoted 16 lines · Greg Earle
Quoted 6 lines · Dan Halbert
Quoted 5 lines · Greg Earle

We use NIS for our maps, but just for fun, I decided to test turning "--ghost" *on* (we default to it off, and we also use "-nobrowse" on our Suns, so we like to keep them consistent), and ...

Quoted 6 lines

Greg, try the latest kernel, 2.6.9-55.0.12, which is now available from
RedHat and has also gone downstream to various other RH-source-based distributions. This works for us. I agree your ghost/non-ghost differences are odd and do not match my experience. But I see differences also based on client load.

Quoted 8 lines

I see that Red Hat just announced/released RHEL 4 Update 6 yesterday:

https://www.redhat.com/archives/nahant-list/2007-November/msg00068.html

It appears that this includes kernel 2.6.9-67. Can I safely assume that this new release quashes this pesky ENOENT bug once and for all?

Try it out.
All I can say is that the 4.6 release kernel has the patches that were used in 2.6.9-55.0.12 to resolve the problem.

Quoted 7 lines

More interestingly/importantly, RHEL 4 Update 6 includes autofs5 as a "Technology Preview". How does the autofs5 code in this new release compare with the mainline code in RHEL 5 Update 1, and is it considered robust enough to use in a production environment that depends heavily (as in, "life or death" - we use the automounter for *everything*) on automounting?

It's the same as is in RHEL 5 U1, except for some changes to allow autofs and autofs5 to be installed at the same time. You still need to use "one or the other", not both.

I'll be keeping RHEL 4 autofs5 in sync with RHEL 5 autofs.

Tech Preview was our only option to get this into RHEL4 as autofs version 4 is already included as a core package, which must continue to be included.

Quoted 8 lines

We started our RHEL 4 Update 5 upgrade cycle a month and a half ago but were stopped dead in our tracks by this bug.

Now that we have a workaround ("--ghost"), we are planning on pushing ahead, but I need to know whether I should try recommending that we instead move to Update 6 rather than continue to use Update 5 with a Band-Aid.

The kernel revision 2.6.9-55.0.12 isn't really a band-aid, it contains a correction.

Whether you go 4.6 with autofs5 is a decision you'll need to make yourself after suitable testing. There is of course the issue that a Tech Preview isn't officially supported so you may have trouble logging bugs. But then you can always report them here and I can log bugs if needed.

Ian