From owner-freebsd-stable@FreeBSD.ORG Wed Apr 23 01:08:29 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4925106564A for ; Wed, 23 Apr 2008 01:08:29 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 843178FC15 for ; Wed, 23 Apr 2008 01:08:29 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m3N18Smt087041; Tue, 22 Apr 2008 21:08:28 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id m3N18Rtd094429 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Apr 2008 21:08:27 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200804230108.m3N18Rtd094429@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 22 Apr 2008 21:07:22 -0400 To: pluknet From: Mike Tancsa In-Reply-To: References: <20080421094718.GY25623@hub.freebsd.org> <200804211537.m3LFbaZA086977@lava.sentex.ca> <200804221501.m3MF1guW092221@lava.sentex.ca> <200804221741.m3MHfYjO092795@lava.sentex.ca> <200804221807.m3MI73bN092981@lava.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: stable@freebsd.org Subject: Re: nfs-server silent data corruption 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: Wed, 23 Apr 2008 01:08:29 -0000 At 04:13 PM 4/22/2008, pluknet wrote: >Hi, I have the same problem with data corruption (with nfe on nfs >server side), >particularly when transferring large files. >Maybe this is somehow associated with the topic. > >My simple test case: >truncate -s 1000m bigfile >^^ here I get zero-filed file >cp bigfile /nfs/mounted >^^ here I get not-at-all-zero-filed file, after uploading to nfs server > >nfs server on 8-CURRENT as of Apr 17 >nfs client on 7.0-STABLE as of Apr 12 Hi, On a RELENG_6 client and the same RELENG_7 (now ULE) server with nfe, all seems to work fine [ns1]# mount /backup/ [ns1]# cp -p j2.txt /backup/ [ns1]# umount /backup/ [ns1]# mount /backup/ [ns1]# cp -p /backup/j2.txt /tmp/j2-copy.txt [ns1]# md5 /tmp/j2-copy.txt MD5 (/tmp/j2-copy.txt) = b0977dceb7b511bb8c542ac4f18c7128 [ns1]# md5 /tmp/j2.txt MD5 (/tmp/j2.txt) = b0977dceb7b511bb8c542ac4f18c7128 [ns1]# cd /tmp [ns1]# truncate -s 1000m bigfile [ns1]# ls -lh bigfile -rw-r--r-- 1 root wheel 1.0G Apr 22 21:03 bigfile [ns1]# md5 bigfile MD5 (bigfile) = e5c834fbdaa6bfd8eac5eb9404eefdd4 [ns1]# cp -p bigfile /backup/ [ns1]# umount /backup/ [ns1]# mount /backup/ [ns1]# cp -p /backup/bigfile /tmp/b2 [ns1]# md5 /tmp/b2 MD5 (/tmp/b2) = e5c834fbdaa6bfd8eac5eb9404eefdd4 [ns1]# ---Mike