From owner-freebsd-current@FreeBSD.ORG Fri Jan 23 22:38:18 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B36CD10656D2 for ; Fri, 23 Jan 2009 22:38:18 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [217.170.79.85]) by mx1.freebsd.org (Postfix) with ESMTP id 6F9DE8FC1C for ; Fri, 23 Jan 2009 22:38:18 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1LQUM8-0000Mi-NE for freebsd-current@freebsd.org; Sat, 24 Jan 2009 01:18:28 +0300 Received: from deprived.panopticon (unknown [192.168.0.34]) by hive.panopticon (Postfix) with ESMTP id B2BF9DE8D for ; Sat, 24 Jan 2009 01:18:42 +0300 (MSK) Received: by deprived.panopticon (Postfix, from userid 1000) id C863E1702D; Sat, 24 Jan 2009 01:18:26 +0300 (MSK) Date: Sat, 24 Jan 2009 01:18:26 +0300 From: Dmitry Marakasov To: freebsd-current@freebsd.org Message-ID: <20090123221826.GB30982@deprived.panopticon> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Subject: NFS data corruption X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 22:38:19 -0000 Hi! I'm using -CURRENT on my new desktop box (due to hardware support issues with 7.x), and I've experienced reproducible data corruptions with NFS. Server: 7.0-RELEASE amd64. Clients: 7.0-RELEASE i386 [no problems] CURRENT i386 [corruption] The problem showed itself as checksum mismatch when building a first port on a new box with distfiles/ mounted via NFS (using amd). For now I have two cases of corruption - in both cases it is single difference of one 128 byte block with file offsets 0x65F872 and 0x61A072. Seems like the corruption only appears once in either server lifetime or mount, as I've checked md5 for all 8GB of distfiles and only had single corruption, i.e. it shows itself once after the start of the client (in first 10-20MB's) and then everything is OK (I was able to build bunch of ports without problems). Is there any way I can help to diagnose and fix the problem? Here's amd.map file which is used to mount this filesystem: --- /defaults type:=nfs;rhost:=hive;opts:=rw,nosuid,noexec,-3,-i,-s,-T * rfs:=/pool/${key} --- Here's uname -a: FreeBSD hades.panopticon 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Fri Jan 23 03:39:16 UTC 2009 root@chrysalis.panopticon:/mnt/usr/obj/mnt/usr/src/sys/HADES i386 -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru