From owner-freebsd-stable@FreeBSD.ORG Thu Oct 16 21:29:32 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AFF78156 for ; Thu, 16 Oct 2014 21:29:32 +0000 (UTC) Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 78807227 for ; Thu, 16 Oct 2014 21:29:32 +0000 (UTC) Received: by mail-oi0-f45.google.com with SMTP id i138so3372854oig.18 for ; Thu, 16 Oct 2014 14:29:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=l0Uw5kUiqW8oiRIEcV6uNuCgGYkX/XAT2gNfnjZE+Yg=; b=0j4xJnToKsTN8RQ0Z97PT/C+DOsK3BwX7NfqbN0p8hA9T5rOJwdozI2NqFsGLO97Ow NE/m84+JDoTgStLoQ8Meftv7a6gW4ZfbNad9MVb+ZGegCRsqPlS5zGg4OiBgCaeRqjHd 4WMhoy0x2a13sqq5eObefig5eLxZESlqGwJf9AZeXl1XF8GyEiJDgtcQBkWBYdmu0dYZ bsufZVxHzKBbZ/czZSro1D2K1gQkPZkqiLpHitV7XMb5zAAlJX2ovzET6cbbqHTiZIyj 4FkZ58U+a5mVG8GhSI3TLxVE0KYY+l11oFx1OV55vFYvR2Ii0+sD9a7wMYST2Ug2SX7U Ffyw== MIME-Version: 1.0 X-Received: by 10.182.246.40 with SMTP id xt8mr3185235obc.59.1413494971813; Thu, 16 Oct 2014 14:29:31 -0700 (PDT) Received: by 10.202.178.8 with HTTP; Thu, 16 Oct 2014 14:29:31 -0700 (PDT) In-Reply-To: References: Date: Thu, 16 Oct 2014 14:29:31 -0700 Message-ID: Subject: Re: nvd disk on nvme controller not detected at boot-time From: Jim Harris To: Maikel Verheijen Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2014 21:29:32 -0000 On Thu, Oct 16, 2014 at 1:43 PM, Maikel Verheijen < Maikel.Verheijen@redwood.com> wrote: > Hi Jim, > > I'm currently running FreeBSD 10.0 with updates from freebsd-update. > Would FreeBSD 10.1-RC be safe for a production environment or would it be > better to wait until the real release? The machine is not used for > production yet, but we do want to go live with it in the near future. I > currently use a =E2=80=9Cworkaround=E2=80=9D, I=E2=80=99m not loading ZFS= at boot time but use a > custom RC script to load the nvd module, test if the nvd0 disk is there, > then load the ZFS module. That seems to work for now, but having it work > =E2=80=9Cout of the box=E2=80=9D would be better, and a lot less prone to= manual mistakes > made by me :) > > I cannot recommend whether 10.1-RC would be safe for a production environment, but you could certainly use 10.1-RC to at least confirm it fixes the issues described. You could also apply these two patches to your 10.0 kernel tree and rebuild just nvme.ko. Best regards, -Jim