On Thu, 2006-08-31 at 10:45 +0100, Matt Bernstein wrote:
> At 11:18 +0800 Ian Kent wrote:
> 
> > On Wed, 2006-08-30 at 20:44 +0100, Matt Bernstein wrote:
> >>
> >> Your patch applied cleanlyish (just line wrapping to deal with), and now
> >> it does *most* of the right things.
> >
> > My mistake, must have broken the patch when I sent it.
> > I was able to duplicate the setup reflected in the log and the mount
> > succeeded.
> >
> > How about we try the patch again but properly formatted.
> 
> Same deal, I think :-\
> 
> Aug 31 10:37:39 laurel automount[20951]: mount(nfs): mounted cream:/export71 
> on /server/cream/export71
> Aug 31 10:37:39 laurel automount[20951]: send_ready: token = 2135
> Aug 31 10:37:39 laurel automount[20951]: mounted /server/cream/export71
> Aug 31 10:37:39 laurel automount[20951]: mount_mount: mount(bind): mounted 
> /server/cream/export71/users type bind on /home/cream/home71
>                                           ^^^^^^^^^^^^^^^^^^^^^^^^
> looks good
> 
> Aug 31 10:37:39 laurel automount[20951]: send_ready: token = 2134
> Aug 31 10:37:39 laurel automount[20951]: mounted /home/cream/home71
> Aug 31 10:37:39 laurel automount[20951]: mount(nfs): nfs: mount failure 
> :/home/cream/home71/mb on /homes/mb
>                                           ^^^^^^^^^^^^^^^
> looks less good

That's just because the nfs mount module calls the bind mount module.
If it gets a fail return from the bind mount it reports it itself.

But I don't see any fails so I don't understand where this is comming
from.

> 
> Aug 31 10:37:39 laurel automount[20951]: send_fail: token = 2133
> Aug 31 10:37:39 laurel automount[20951]: failed to mount /homes/mb
> 
> Maybe my auto.master is not right? Here are the relevant entries:

Don't this this has anything to do with this.

Ian


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

Reply via email to