Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Jul 2005 13:21:27 -0700
From:      Alfred Perlstein <alfred@freebsd.org>
To:        Pawel Jakub Dawidek <pjd@FreeBSD.org>
Cc:        cvs-src@FreeBSD.org, src-committers@FreeBSD.org, Paul Saab <ps@FreeBSD.org>, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/sys/nfsclient nfs_socket.c
Message-ID:  <20050719202127.GU40423@elvis.mu.org>
In-Reply-To: <20050718071812.GF46538@darkness.comp.waw.pl>
References:  <200507180212.j6I2CHkP074749@repoman.freebsd.org> <20050718071812.GF46538@darkness.comp.waw.pl>

next in thread | previous in thread | raw e-mail | index | archive | help
* Pawel Jakub Dawidek <pjd@FreeBSD.org> [050718 00:18] wrote:
> On Mon, Jul 18, 2005 at 02:12:17AM +0000, Paul Saab wrote:
> +> ps          2005-07-18 02:12:17 UTC
> +> 
> +>   FreeBSD src repository
> +> 
> +>   Modified files:
> +>     sys/nfsclient        nfs_socket.c 
> +>   Log:
> +>   Fix for a NFS soft mounts bug where if the number of retries exceeds
> +>   the max rexmits, the request was not being bounced back with a
> +>   ETIMEDOUT error.
> 
> I saw ESTALE errors on NFS clients after rebooting NFS server.
> umount/mount was the only way to fix it.
> Your commit should fix my problem? My machines are running 5-STABLE.

Unlikely, the source of such a problem is probably that the order
of mounted filesystems has changed and a different fsid was given
to your exported fs.

One way to fix it is to make sure that your fses are mounted in the
right order each time.  Or you can do a hack whereby exporting loads
the fsid from a persistent file in the filesystem.



-- 
- Alfred Perlstein
- email: bright@mu.org cell: 408-480-4684



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050719202127.GU40423>