From owner-freebsd-fs@FreeBSD.ORG Thu Jun 8 21:29:55 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 819B916A613; Thu, 8 Jun 2006 17:46:18 +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 A849943D49; Thu, 8 Jun 2006 17:46:17 +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 k58HkGQo032468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 8 Jun 2006 13:46:16 -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 k58HkAG2033423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Jun 2006 13:46:10 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) From: Mikhail Teterin Organization: Virtual Estates, Inc. To: fs@freebsd.org, mckusick@freebsd.org Date: Thu, 8 Jun 2006 13:46:04 -0400 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606081346.04908.mi+mx@aldan.algebra.com> X-Virus-Scanned: ClamAV 0.88/1520/Wed Jun 7 17:47:18 2006 on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 Cc: Subject: 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: Thu, 08 Jun 2006 21:29:55 -0000 Our amd64 6.1-STABLE system is used to collect backup dumps from production systems (mostly -- Solaris) via NFS. When in progrss, the dumps arrive at an average rate of 20Mb/s. Every once in a while I notice a discrepancy in the amount of used space on the backup FS as reported by df vs. that reported by the total du. Unmounting the FS and fsck-ing it fixes the problem with fsck reporting (despite the clean unmount): SUMMARY BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? yes The FS is intended for very few very large files and was created with "newfs -b 65536 -O1" (no softupdates). This workaround (explicit fsck) is acceptable for us, but it is a sign of some kind of rot, and I thought, you'd like to know... Yours, -mi