From owner-freebsd-stable@freebsd.org Tue Oct 6 16:06:10 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C01759D0260 for ; Tue, 6 Oct 2015 16:06:10 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [199.48.133.146]) by mx1.freebsd.org (Postfix) with ESMTP id A80B1DBB for ; Tue, 6 Oct 2015 16:06:09 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from marvin.beer.town (unknown [76.164.8.130]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 3363C56483; Tue, 6 Oct 2015 11:06:03 -0500 (CDT) Subject: Re: Dell NVMe issues To: Sean Kelly , FreeBSD-STABLE Mailing List References: Cc: Jim Harris From: Eric van Gyzen X-Enigmail-Draft-Status: N1110 Message-ID: <5613F16A.8010901@vangyzen.net> Date: Tue, 6 Oct 2015 11:06:02 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Oct 2015 16:06:10 -0000 On 10/06/2015 10:18, Sean Kelly wrote: > Back in May, I posted about issues I was having with a Dell PE R630 with 4x800GB NVMe SSDs. I would get kernel panics due to the inability to assign all the interrupts because of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199321 . Jim Harris helped fix this issue so I bought several more of these servers, Including ones with 4x1.6TB drives… > > while the new servers with 4x800GB drives still work, the ones with 4x1.6TB drives do not. When I do a > zpool create tank mirror nvd0 nvd1 mirror nvd2 nvd3 > the command never returns and the kernel logs: > nvme0: resetting controller > nvme0: controller ready did not become 0 within 2000 ms > > I’ve tried several different things trying to understand where the actual problem is. > WORKS: dd if=/dev/nvd0 of=/dev/null bs=1m > WORKS: dd if=/dev/zero of=/dev/nvd0 bs=1m > WORKS: newfs /dev/nvd0 > FAILS: zpool create tank mirror nvd[01] > FAILS: gpart add -t freebsd-zfs nvd[01] && zpool create tank mirror nvd[01]p1 > FAILS: gpart add -t freebsd-zfs -s 1400g nvd[01[ && zpool create tank nvd[01]p1 > WORKS: gpart add -t freebsd-zfs -s 800g nvd[01] && zpool create tank nvd[01]p1 > > NOTE: The above commands are more about getting the point across, not validity. I wiped the disk clean between gpart attempts and used GPT. > > So it seems like zpool works if I don’t cross past ~800GB. But other things like dd and newfs work. > > When I get the kernel messages about the controller resetting and then not responding, the NVMe subsystem hangs entirely. Since my boot disks are not NVMe, the system continues to work but no more NVMe stuff can be done. Further, attempting to reboot hangs and I have to do a power cycle. > > Any thoughts on what the deal may be here? > > 10.2-RELEASE-p5 > > nvme0@pci0:132:0:0: class=0x010802 card=0x1f971028 chip=0xa820144d rev=0x03 hdr=0x00 > vendor = 'Samsung Electronics Co Ltd' > class = mass storage > subclass = NVM Try this: sysctl vfs.zfs.vdev.trim_on_init=0 zpool create tank mirror nvd[01] Eric