From owner-freebsd-stable@FreeBSD.ORG Wed Jan 31 07:48:50 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0DAC916A40A for ; Wed, 31 Jan 2007 07:48:50 +0000 (UTC) (envelope-from wayne@manor.msen.com) Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id C594713C4B2 for ; Wed, 31 Jan 2007 07:48:49 +0000 (UTC) (envelope-from wayne@manor.msen.com) Received: from manor.msen.com (localhost [127.0.0.1]) by manor.msen.com (8.12.11/8.12.11) with ESMTP id l0V7OdFd036495 for ; Wed, 31 Jan 2007 02:24:39 -0500 (EST) (envelope-from wayne@manor.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.12.11/8.12.11/Submit) id l0V7OZpf036494 for freebsd-stable@freebsd.org; Wed, 31 Jan 2007 02:24:35 -0500 (EST) (envelope-from wayne) Date: Wed, 31 Jan 2007 02:24:35 -0500 From: "Michael R. Wayne" To: freebsd-stable@freebsd.org Message-ID: <20070131072435.GR63341@manor.msen.com> Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Filesystem hang on 3ware 6.2 system X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2007 07:48:50 -0000 We have a nubmer of similar machines that were initiallly formated with 6.2 before it was released and have subsequently been upgraded to 6.2-RELEASE with no issues. So, we upgraded a 6.1 box which has been running fine as long as the nightly dumps do not use -L to take snapshots. Once it was upgraded to 6.2, we enabled -L on the nightly dumps and it hung on the first try. So, I'm suspecting that 6.1 has left SOMEthing on the filesystem which is corrupt. For the moment. we have once again removed -L from the nightly dumps but, other than a complete fsck, is there any other suggested action? 6.2-RELEASE twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0x9c00-0x9c0f mem 0xfc9ffc00-0xfc9ffc0f,0xfc000000-0xfc7fffff irq 20 at device 1.0 on pci2 twe0: [GIANT-LOCKED] twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048 /\/\ \/\/