From owner-freebsd-current@FreeBSD.ORG Fri Sep 9 11:08:55 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 767AE1065670 for ; Fri, 9 Sep 2011 11:08:55 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gw0-f49.google.com (mail-gw0-f49.google.com [74.125.83.49]) by mx1.freebsd.org (Postfix) with ESMTP id 310C28FC18 for ; Fri, 9 Sep 2011 11:08:54 +0000 (UTC) Received: by gwb1 with SMTP id 1so1241612gwb.36 for ; Fri, 09 Sep 2011 04:08:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=HOW3AMhLmZZSn9QtWNM6CgICQnU69j+jzzoewyKxDPc=; b=WChFBYXi32h0iKI2xfw+mpStJl9sNbMPfvWJ7deAUXJdYJZnVlrBBdwY3SNNJnwrkB W01OXl8+LroaFINv62Ju7dsSDqB1Ctgfmcos1fVpBPhTF9WN59ymoudy/JVv/ne+msee eRVWl5YgBG6NohKYtEmeE4pknktB9zcZXRqYI= MIME-Version: 1.0 Received: by 10.236.37.230 with SMTP id y66mr11327816yha.10.1315566534518; Fri, 09 Sep 2011 04:08:54 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.236.103.6 with HTTP; Fri, 9 Sep 2011 04:08:54 -0700 (PDT) In-Reply-To: References: <815930668.115706.1315407799946.JavaMail.root@mail-01.cse.ucsc.edu> Date: Fri, 9 Sep 2011 19:08:54 +0800 X-Google-Sender-Auth: tQIFEoACrENglYtHWLVHLQCUCaY Message-ID: From: Adrian Chadd To: Matt Thyer Content-Type: text/plain; charset=ISO-8859-1 Cc: Tim Gustafson , freebsd-current@freebsd.org Subject: Re: RELENG_8 / mpt / zpool Errors X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 11:08:55 -0000 On 9 September 2011 18:32, Matt Thyer wrote: > Harder solutions are: > > A) Fix the driver .. which is the only way FreeBSD improves, so. You choose. :) Also: A1) Post lots of debugging info to the list, be very friendly and helpful, see if any developers are willing to help you figure and fix it A2) If not, look at paying a small (say $1k) bounty to get it fixed. :) Adrian