From owner-freebsd-fs@FreeBSD.ORG Fri Apr 12 22:20:06 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 7258B3E2 for ; Fri, 12 Apr 2013 22:20:06 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:243]) by mx1.freebsd.org (Postfix) with ESMTP id 56D1973 for ; Fri, 12 Apr 2013 22:20:06 +0000 (UTC) Received: from omta02.emeryville.ca.mail.comcast.net ([76.96.30.19]) by qmta13.emeryville.ca.mail.comcast.net with comcast id P3Vb1l0040QkzPwADAL6BF; Fri, 12 Apr 2013 22:20:06 +0000 Received: from koitsu.strangled.net ([67.180.84.87]) by omta02.emeryville.ca.mail.comcast.net with comcast id PAL51l00J1t3BNj8NAL5cr; Fri, 12 Apr 2013 22:20:05 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 437A173A33; Fri, 12 Apr 2013 15:20:05 -0700 (PDT) Date: Fri, 12 Apr 2013 15:20:05 -0700 From: Jeremy Chadwick To: freebsd-fs@freebsd.org Subject: Re: A failed drive causes system to hang Message-ID: <20130412222005.GA82884@icarus.home.lan> References: <51672164.1090908@o2.pl> <41A207817BC94167B0C94133EC0DFD68@multiplay.co.uk> <51687881.4080005@o2.pl> <20130412212207.GA81897@icarus.home.lan> <5168864A.2090602@sneakertech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5168864A.2090602@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=1365805206; bh=o5qa+F35UcOm/TqF24SpdK6oW/P9DaSsqWLd5K9syeE=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=XUvkZnn9Oevc5jlgGFFD+XQclnSIMcbpoanVStjC2Q8+JduEurjO3aSiHSqIboWyD aIoJH+bQrxY3ZTtsM5tv6w8ZMYHCm6A2EkNjdbNahTW7xhdgPaNm6r/5/RMvO/w6RJ 4foSPV4z0gXNUQw+Ibwa2lRyrFHdtsIGW38gRM1BHFR2wSGGZPywVAs5h3IT177yqU QvfZjvekEXaOiq6CZzTklWZ8zC5Vbf6SK6TVSBQk1eVR3A1n/l5YnfD/kQi9o3vZnZ t2/Ad0M18Vy7/lDI7mX7QO+PT9LdBir7h2+8OGTjaVwt/lxewYFY5sCgl1Iukq1wA+ wwByZ390DAoaQ== 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: Fri, 12 Apr 2013 22:20:06 -0000 On Fri, Apr 12, 2013 at 06:10:18PM -0400, Quartz wrote: > > >While PC-BSD is based on FreeBSD, > > Wait, isn't pcbsd exactly the same as vanilla freebsd except that > kde/bash/trueos/etc are pre-installed? Do they have their own > version of zfs or low level library differences or something? Off-topic, so I will not be responding past this point: Let's say I have a router maintained/made by XYZ company that runs Linux. I have problems with this device, but am unsure what the reason is or what the cause is. Do I mail the LKML about the issue or do I go to the vendor? The correct answer is: you start by going to the vendor. Alternately one can involve both (ex. vendor and CC the LKML). The fact that it's a "purchased piece of hardware" has no bearing -- the methodology of support inquiries is the same. My point is that the PC-BSD folks need to be made aware of this issue, so their iXSystems folks can help out if necessary and so on. If they're left out of the loop, then that's bad for everyone. -- | 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 |