From owner-freebsd-fs@FreeBSD.ORG Wed Sep 8 08:49:10 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 90EF01065674 for ; Wed, 8 Sep 2010 08:49:10 +0000 (UTC) (envelope-from spork@bway.net) Received: from xena.bway.net (xena.bway.net [216.220.96.26]) by mx1.freebsd.org (Postfix) with ESMTP id 34B2F8FC15 for ; Wed, 8 Sep 2010 08:49:10 +0000 (UTC) Received: (qmail 26881 invoked by uid 0); 8 Sep 2010 08:27:32 -0000 Received: from unknown (HELO ?10.3.2.41?) (spork@96.57.144.66) by smtp.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 8 Sep 2010 08:27:32 -0000 Date: Wed, 8 Sep 2010 04:22:19 -0400 (EDT) From: Charles Sprickman X-X-Sender: spork@hotlap.local To: freebsd-fs@freebsd.org, freebsd-scsi@freebsd.org Message-ID: User-Agent: Alpine 2.00 (OSX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: Subject: 7.3 or 7-STABLE? 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: Wed, 08 Sep 2010 08:49:10 -0000 Hello, Quick question... I'm still having issues with an amd64 box and corruption on a largish (1.3T) filesystem. http://www.listware.net/201007/freebsd-fs/13111-72-ufs2-corruption.html - sorry for the crappy archive I've let the RAID controller run a few full verifies, and that comes back clean, the hardware is fine (pre-production it went through insanely long memtest runs, a week of build/installworld, etc.). Only after putting some real mail load on it did this start happening. For all I know, it could have been one bad panic that mangled things and fsck simply cannot fix it properly. That said, before even taking it down for a long rsync off to another host, newfs, then rsync back, I'd like to upgrade to 7.3 or 7-stable. The reason for choosing both -fs and -scsi is that I'd like some feedback from both groups on the two things I'm most suspicious of - UFS itself and the mfi driver. If neither has had any interesting changes in -stable, I'll go to 7.3 (at 7.2 now). If there are, then I might give -stable a shot... If the upgrade doesn't help, then I'll spend the time moving the data off, newfs'ing /spool and bringing the data back. If that doesn't work, then it's 8.1 (unless someone has a really compelling argument on making that step 1). If this were my box, I'd be putting more time into this, but the client is having numerous issues with cashflow, and I'm not looking to put out more hours than I may get paid for. Sad but true, and perhaps a lame excuse for sloppy administration... Thanks, Charles