From owner-freebsd-current@FreeBSD.ORG Wed Jan 11 18:14:47 2012 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 C1DA1106567A for ; Wed, 11 Jan 2012 18:14:47 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2001:470:1f0b:105e::1ea]) by mx1.freebsd.org (Postfix) with ESMTP id 826538FC17 for ; Wed, 11 Jan 2012 18:14:47 +0000 (UTC) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id 60DFAAAE02; Wed, 11 Jan 2012 18:14:46 +0000 (UTC) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=us-ascii From: Stefan Bethke In-Reply-To: <20120111165714.GA46594@cons.org> Date: Wed, 11 Jan 2012 19:14:44 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20120111165714.GA46594@cons.org> To: Martin Cracauer X-Mailer: Apple Mail (2.1251.1) Cc: freebsd-current@freebsd.org Subject: Re: Data corruption over NFS in -current 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: Wed, 11 Jan 2012 18:14:47 -0000 Am 11.01.2012 um 17:57 schrieb Martin Cracauer: > I'm sorry for the unspecific bug report but I thought a heads-up is > better than none. >=20 > $ uname -a > FreeBSD wings.cons.org 10.0-CURRENT FreeBSD 10.0-CURRENT #2: Wed Dec > 28 12:19:21 EST 2011 > cracauer@wings.cons.org:/usr/src/sys/amd64/compile/WINGS amd64 I'm sure Rick will want to know which NFS version, which client code = (default new code I'm assuming) and which mount options... > I see filesystem corruption on NFS filesystems here. I am running a > heavy shellscript that is noodling around with ascii files assembling > them with awk and whatnot. Some actions are concurrent with up to 21 > forks doing full-CPU load scripting. This machine is a K8 with a > total of 8 cores, diskless NFS and memory filesystem for /tmp. >=20 > I observe two problems: > - for no reason whatsoever, some files change from my=20 > (user/group) cracauer/wheel to root/cracauer > - the same files will later be corrupted. The beginning of the file > is normal but then it has what looks like parts of /usr/ports, > including our CVS files and binary junk, mostly zeros >=20 > I did do some ports building lately but not at the same time that this > problem manifested itself. I speculate some ports blocks were still > resident in the filesystem buffer cache. >=20 > Server is Linux. >=20 > Martin > --=20 > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > Martin Cracauer http://www.cons.org/cracauer/ > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" --=20 Stefan Bethke Fon +49 151 14070811