Ah sorry Bryn,
Was waiting for customer to finish test before continuing, but yes. It looks very similar to another issue that was in EL4 autofs. I'm waiting for customer to respond to test kernel with autofs patches, then will update this bz.

(In reply to comment #2)
> Ah sorry Bryn,
>
> Was waiting for customer to finish test before continuing, but yes. It looks
> very similar to another issue that was in EL4 autofs. I'm waiting for customer
> to respond to test kernel with autofs patches, then will update this bz.
Which kernel revision?

(In reply to comment #3)
> (In reply to comment #2)
> > Ah sorry Bryn,
> >
> > Was waiting for customer to finish test before continuing, but yes. It looks
> > very similar to another issue that was in EL4 autofs. I'm waiting for customer
> > to respond to test kernel with autofs patches, then will update this bz.
>
> Which kernel revision?
The kernel provided was revision 107 and the RHEL-5.3 autofs patch
series went into revision 106 so we'll have to wait and see how this
goes. I expect it will take a while since, if this is an example
of the autofs issue of this type included in corrections of the
series, then it happens only very occasionally.
Ian

Ian,
I spoke to Wade who told me that you have some patches that fix this bug. Are there any test packages available incorporating the patches? I would like the customers for the attached ITs (both mine) to test them out.

All the patches are in the current pre-release RHEL-5.3 kernel.
This is the best candidate for customer testing unless they have
a need to retain their current kernel, in which case I can make
a scratch build for the kernel the customer needs to use.
Ian

Looking at the IT I've noticed another potential problem.
The "exportfs" output doesn't tell us what export is the
root of the export tree. I presume /home1/shares has the
fsid=1 option and is the root of the export tree. But we
also can't tell if the subordinate mounts in the tree have
the "nohide" option. If that is the case then we know that
the NFS kernel client mounting can cause autofs revision
0.rc2.88 to become confused.
The issue has been addressed in a later revision of autofs
so please be aware of it.
Ian