Re: Waking up server during boot prevents NFS mounts after upgrade to etch

[bob@proulx.com (Bob Proulx)]

Malte Forkel wrote:
> After upgrading the clients from sarge to etch, mounting NFS volumes
> does not work anymore if the server wasn't up already.

I think that should be considered a bug.  Traditional behavior should
have the clients block waiting for the server to come online and then
continue normally after that.  If you agree then please file a bug.

This might help.  Are you aware of the NFS mount option 'bg'?

  bg
    If the first NFS mount attempt times out, retry the mount in the
    background.  After a mount operation is backgrounded, all
    subsequent mounts on the same NFS server will be backgrounded
    immediately, without first attempting the mount.  A missing mount
    point is treated as a timeout, to allow for nested NFS mounts.

This is a traditional method of breaking circular dependencies.  But
it might help as a workaround to the behavior that you are reporting.

> It takes the server about 1 minute to boot. If the server is up before 
> the client boots, NFS mounts work fine.

Lots of things changed.  I did not try to recreate your bad behavior
but it reads like a bug to me.

> With or without asynchronous mounting. So, may be I have some sort
> of a timing problem?

Using sync versus async is completely different and unrelated.  That
has to do with the protocol used after the clients have mounted.

Bob