Received: (from majordomo@localhost) by oss.sgi.com (8.11.3/8.11.3) id f381Ojo01729 for linux-xfs-outgoing; Sat, 7 Apr 2001 18:24:45 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.3/8.11.3) with ESMTP id f381OiM01726 for ; Sat, 7 Apr 2001 18:24:44 -0700 Received: from zeus-fddi.americas.sgi.com (128-162-8-103.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id SAA04033 for ; Sat, 7 Apr 2001 18:24:44 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id UAA1400699; Sat, 7 Apr 2001 20:23:26 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.184.86]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id UAA25713; Sat, 7 Apr 2001 20:23:26 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.0/SGI-client-1.7) via ESMTP id f381PPI14606; Sat, 7 Apr 2001 20:25:26 -0500 Message-Id: <200104080125.f381PPI14606@jen.americas.sgi.com> To: Lennert Buytenhek cc: linux-xfs@oss.sgi.com Subject: Re: "Bad write on page" ? References: <20010407195109.A16180@gnu.org> Comments: In-reply-to Lennert Buytenhek message dated "Sat, 07 Apr 2001 19:51:09 -0400." Date: Sat, 07 Apr 2001 20:25:25 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > XFS likes me, I just know it. I get heaps and heaps of this while doing a > "dd if=largefile of=copyoflargefile bs=32768k". > > > Bad write on page 0xc1010130 > Bad write on page 0xc10331ec This error message relates to flushing pages out beyond the end of file, the only place I saw it was via NFS, the code checked in on the 5th stopped it happening for me. At the moment I need to establish if these bugs are still there in the current development cvs tree, or people are still running kernels with old code in them. Presuming this is a current kernel, then we need more information about what you were doing to create the problem. a) was NFS involved, if so mount options and nfsd config options used, b) are you still filling the filesystem c) how big was the file d) machine configuration Thanks Steve