From owner-freebsd-stable@FreeBSD.ORG Sun Mar 19 05:33:42 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54F0516A400 for ; Sun, 19 Mar 2006 05:33:42 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1787A43D45 for ; Sun, 19 Mar 2006 05:33:42 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id F2CE51A3C1B; Sat, 18 Mar 2006 21:33:41 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 50F6551447; Sun, 19 Mar 2006 00:33:41 -0500 (EST) Date: Sun, 19 Mar 2006 00:33:41 -0500 From: Kris Kennaway To: Rong-En Fan Message-ID: <20060319053341.GA70205@xor.obsecurity.org> References: <6eb82e0603182119w5eff748fneffc46e2692447a7@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline In-Reply-To: <6eb82e0603182119w5eff748fneffc46e2692447a7@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: NFS data corruption listed in 6.1 show stopper X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Mar 2006 05:33:42 -0000 --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 19, 2006 at 12:19:04AM -0500, Rong-En Fan wrote: > Hi, >=20 > We are planning to upgrade a NFS server from 5.x to 6.x. However, > we found there is a show stopper of 6.1 about NFS data corruption. > >From the todo page, it says this item is worked in progress. Is this > has been fixed already or not yet? From the description, it is found > by running fsx (in regression/fsx?), can somebody show how to > reproduce this? We would like to do some tests. It's not yet fixed. I'm able to reproduce it by running 3 fsx instances on a TCP mount; one of them will crash after some time (a few seconds .. hours). This problem also exists on 5.x servers. I'm not seeing corruption from UDP mounts. Kris --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEHO00Wry0BWjoQKURApN7AKDGE3UfrJ0S7Pbs76J/22AMLYqzAgCfQq8p dPCwPlwPZUkDnAYrkMiSRds= =KxuI -----END PGP SIGNATURE----- --BOKacYhQ+x31HxR3--