From owner-freebsd-fs@FreeBSD.ORG Fri Jun 9 18:59:03 2006 Return-Path: X-Original-To: fs@freebsd.org Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7045616A418 for ; Fri, 9 Jun 2006 18:59:03 +0000 (UTC) (envelope-from mi+mx@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id A804C43D70 for ; Fri, 9 Jun 2006 18:59:02 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by aldan.algebra.com (8.13.6/8.13.6) with ESMTP id k59Iwvgo036637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 9 Jun 2006 14:58:58 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from [172.21.130.86] (mx-broadway [38.98.68.18]) by corbulon.video-collage.com (8.13.6/8.13.6) with ESMTP id k59IwpC6010641 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Jun 2006 14:58:52 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) From: Mikhail Teterin Organization: Virtual Estates, Inc. To: Scott Long Date: Fri, 9 Jun 2006 14:58:46 -0400 User-Agent: KMail/1.9.1 References: <20060609065656.31225.qmail@web30313.mail.mud.yahoo.com> <200606091333.42619.mi+mx@aldan.algebra.com> <4489C0B5.3010902@samsco.org> In-Reply-To: <4489C0B5.3010902@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200606091458.46504.mi+mx@aldan.algebra.com> X-Virus-Scanned: ClamAV 0.88/1523/Fri Jun 9 03:10:10 2006 on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 Cc: fs@freebsd.org Subject: Re: heavy NFS writes lead to corrup summary in superblock X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jun 2006 18:59:03 -0000 п'ятниця 09 червень 2006 14:40, Scott Long написав: > Well, before we get too far off on tangents, would you mind running > dumpfs on the filesystem and posting the first block of information? Do you want this now, or when/if I see the corruption again? > It's hard to beleive that NFS would be responsible for corrupting the > filesystem. You should be able to have a consistent and correct unmount > regardless of whether NFS is in use or what options it is using. The other potential "oddity" is that the files are eagerly awaited (via kevent()) by a process running on my NFS server, which mmaps the freshly written chunks (as soon as kevent() returns) and compresses them onto another filesystem. It looks like this: 20060609:14:53:03: mzip: the input size grew from 201031680 to 201064448. Ok... 20060609:14:53:03: mzip: mmap-ing 32768 bytes of /staging/gonzo:4100/TD_THEIR_211-060609-145243.dmp (201064448) starting at 201031680 20060609:14:53:03: mzip: eaten: 32768 of 32768, produced 0 20060609:14:53:03: mzip: Unmapping 32768 bytes starting at 0x80052c000 As soon as the dump is over, and the last portion of it is compressed, the dump is deleted. None of this should be causing the corruption I observed a few times, but any of it could, for it is all mildly unusual :-/ Yours, -mi