From owner-freebsd-fs@FreeBSD.ORG Sun Mar 24 15:37:21 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3961DA9B for ; Sun, 24 Mar 2013 15:37:21 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:16]) by mx1.freebsd.org (Postfix) with ESMTP id 1B98C71 for ; Sun, 24 Mar 2013 15:37:21 +0000 (UTC) Received: from omta22.emeryville.ca.mail.comcast.net ([76.96.30.89]) by qmta01.emeryville.ca.mail.comcast.net with comcast id FScw1l0051vN32cA1TdMAz; Sun, 24 Mar 2013 15:37:21 +0000 Received: from koitsu.strangled.net ([67.180.84.87]) by omta22.emeryville.ca.mail.comcast.net with comcast id FTdL1l0061t3BNj8iTdLwu; Sun, 24 Mar 2013 15:37:20 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 363B273A1C; Sun, 24 Mar 2013 08:37:20 -0700 (PDT) Date: Sun, 24 Mar 2013 08:37:20 -0700 From: Jeremy Chadwick To: Quartz Subject: Re: ZFS: Failed pool causes system to hang Message-ID: <20130324153720.GA3983@icarus.home.lan> References: <20130321044557.GA15977@icarus.home.lan> <514AA192.2090006@sneakertech.com> <20130321085304.GB16997@icarus.home.lan> <514B4D38.6090101@sneakertech.com> <514E166A.5070409@sneakertech.com> <20130323225237.GA85482@icarus.home.lan> <514E91D7.2020209@sneakertech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <514E91D7.2020209@sneakertech.com> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1364139441; bh=HNVxiMkyDjRZfJfvvmN0udnhEPm9twbKHcQyTsGxzj8=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=TOPyUlsbBnqaAmZm+fugJSTePDB4/NgjoEq7v4ZPVipjG+bTycm6vPGwTF+j9X6+x 4VGwyNSBfNf0yVt459a9YrRzRFVQ/Y/ZvE/hn/CcxsWxI5PoCqcjz9nqm79jFeoBJ6 wc+CTLG8DkPsZT39OZ4oIguvUBsB7hwAV4oA029AbXCE9uvit2DpCOtjOaCNTIDUP/ 1KYj6BJRNQR81XVqZ5fG+TONbwwIqWswP80TJGQJv1X2utLnK4ge8RhPrOPxCJK1uE CruVMhFhxyCxURL+TNRwAiGdzQtwhelIMJ4mINXfVfqKDie7/vnGG7uO4ATwAyJUmC VpuSmx5TnusoA== Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Mar 2013 15:37:21 -0000 On Sun, Mar 24, 2013 at 01:40:39AM -0400, Quartz wrote: > http://sneakertech.com/-/dmesg.txt > > Honestly I have my doubts that anything in there will shed > particular light on my zfs issue. From what I can tell this appears > to be common to zfs cross platform (at least, solaris people have > complained about this, and it looks like openindiana might be > affected too). In this case/at this point I wanted dmesg output so I could provide you working /boot/loader.conf lines for your configuration, with regards to "wiring down" device names. If you mess with controllers (e.g. disable one in the BIOS), this may break. Here you go: # "Wire down" device names (ada[0-5]) to each individual port # on the SATA/AHCI controller. This ensures that if we reboot # with a disk missing, the device names stay the same, and stay # attached to the same SATA/AHCI controller. # http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html # # ada[01] = JMicron JMB363 # ada[234567] = Intel ICH10 # hint.scbus.0.at="ahcich0" hint.scbus.1.at="ahcich1" hint.scbus.2.at="ahcich2" hint.scbus.3.at="ahcich3" hint.scbus.4.at="ahcich4" hint.scbus.5.at="ahcich5" hint.scbus.6.at="ahcich6" hint.scbus.7.at="ahcich7" hint.ada.0.at="scbus0" hint.ada.1.at="scbus1" hint.ada.2.at="scbus2" hint.ada.3.at="scbus3" hint.ada.4.at="scbus4" hint.ada.5.at="scbus5" hint.ada.6.at="scbus6" hint.ada.7.at="scbus7" -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |