Red Hat Bugzilla – Bug 448936
do_mount_indirect: indirect trigger not valid
Last modified: 2010-10-22 21:34:24 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5
Description of problem:
When running 'find' on a sub-directory (only one level down) of an automount (using NFS), the find returns "No such file or directory" on the first attempt, but then works fine on the second attempt. So it occurs every time the directory isn't mounted.
find /home/test/dir/subdir - fails with "find: /home/test/dir/subdir: No such file or directory"
find /home/test/dir - works
find /home/test/dir/subdir/otherdir - works
do_mount_indirect: indirect trigger not valid or already mounted /home/test/dir/subdir
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Setup an NFS export
2. Create an automount (we're using NIS+ with niscompat)
3. Run 'find' on a sub-directory of that mount
find: /path/to/subdir: No such file or directory
A listing of found files should have been returned.
This was on a 5.1 system, with the kernel and autofs updated to the 5.2 versions.
I have the the output from automount run in debug mode, but I would need the bug
to be private as it contains sensitive data.
(In reply to comment #1)
> I have the the output from automount run in debug mode, but I would need the bug
> to be private as it contains sensitive data.
Email it directly to me.
Is there any movement on this bug. I believe I am having the same issue.
(In reply to comment #4)
> Is there any movement on this bug. I believe I am having the same issue.
Yes, but it's being worked on in another bug.
I believe this is a kernel bug and I have patches to address
it but I'm not sure how to make a test kernel available?
Which other bug is this being worked on? I'd like to track it.
(In reply to comment #6)
> Which other bug is this being worked on? I'd like to track it.
I don't think that bug is public, sorry.
The current status is that I have identified a mistake in the
patches and I'll be building test kernels soon. We will just
need to find a way to make them available to you for testing.
Unfortunately, there have been a few really difficult issues
reported recently and I'm struggling to fix them.
Sorry for the delay and inconvenience.
I'll get back to this bug as soon as I can.
Has a test kernel which includes a fix for this problem been built yet?
(In reply to comment #8)
> Has a test kernel which includes a fix for this problem been built yet?
It has, how can I make it available to you?
Could you place it on an http or ftp server?
(In reply to comment #10)
> Could you place it on an http or ftp server?
Should have asked, what arches?
(In reply to comment #11)
> (In reply to comment #10)
> > Ian,
> > Could you place it on an http or ftp server?
> Should have asked, what arches?
I've built and uploaded kernels for i686 and x86_64 to
The corrections for this bug are covered by the changes
committed for bug 452139.
Don Zickus has included these patches in the test kernel
kernel-2.6.18-107.el5 which can be download from
Thanks Ian. I've tested Don's kernel build (x86_64), and verified that it did fix the problem.
This issue has been addressed in the current RHEL-5.3 release
kernel. I'm closing this bug as CURRENTRELEASE to reflect this.