Re: Dell NVMe issues

2015-10-06 Thread Jim Harris
On Tue, Oct 6, 2015 at 11:46 AM, Steven Hartland wrote: > On 06/10/2015 19:03, Jim Harris wrote: > > > > On Tue, Oct 6, 2015 at 9:42 AM, Steven Hartland < > kill...@multiplay.co.uk> wrote: > >> Also looks like nvme exposes a timeout_period sysctl you could try >> increasing that as it could be to

Re: Dell NVMe issues

2015-10-06 Thread Steven Hartland
On 06/10/2015 19:03, Jim Harris wrote: On Tue, Oct 6, 2015 at 9:42 AM, Steven Hartland mailto:kill...@multiplay.co.uk>> wrote: Also looks like nvme exposes a timeout_period sysctl you could try increasing that as it could be too small for a full disk TRIM. Under CAM SCSI da sup

Re: Dell NVMe issues

2015-10-06 Thread Jim Harris
On Tue, Oct 6, 2015 at 9:42 AM, Steven Hartland wrote: > Also looks like nvme exposes a timeout_period sysctl you could try > increasing that as it could be too small for a full disk TRIM. > > Under CAM SCSI da support we have a delete_max which limits the max single > request size for a delete

Re: Dell NVMe issues

2015-10-06 Thread Steven Hartland
Also looks like nvme exposes a timeout_period sysctl you could try increasing that as it could be too small for a full disk TRIM. Under CAM SCSI da support we have a delete_max which limits the max single request size for a delete it may be we need something similar for nvme as well to prevent

Re: Dell NVMe issues

2015-10-06 Thread Steven Hartland
As a guess you're timing out the full disk TRIM request. Try: sysctl vfs.zfs.vdev.trim_on_init=0 and then re-run the create. On 06/10/2015 16: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 i

Re: Dell NVMe issues

2015-10-06 Thread Sean Kelly
> On Oct 6, 2015, at 11:06 AM, Eric van Gyzen wrote: > > Try this: > >sysctl vfs.zfs.vdev.trim_on_init=0 >zpool create tank mirror nvd[01] > That worked. So my guess is the controller/FreeBSD is timing out while zpool asks the drive to TRIM all 1.6TB?

Re: Dell NVMe issues

2015-10-06 Thread Eric van Gyzen
On 10/06/2015 11:10, Sean Kelly wrote: > >> On Oct 6, 2015, at 11:06 AM, Eric van Gyzen > > wrote: >> >> Try this: >> >>sysctl vfs.zfs.vdev.trim_on_init=0 >>zpool create tank mirror nvd[01] >> > > That worked. So my guess is the controller/FreeBSD is timing out whi

Re: Dell NVMe issues

2015-10-06 Thread Eric van Gyzen
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 >

Re: Dell NVMe issues

2015-10-06 Thread Slawa Olhovchenkov
On Tue, Oct 06, 2015 at 10:35:57AM -0500, Sean Kelly wrote: > > > > On Oct 6, 2015, at 10:29 AM, Slawa Olhovchenkov wrote: > > > > On Tue, Oct 06, 2015 at 10:18:11AM -0500, Sean Kelly wrote: > > > >> Back in May, I posted about issues I was having with a Dell PE R630 with > >> 4x800GB NVMe S

Re: Dell NVMe issues

2015-10-06 Thread Sean Kelly
> On Oct 6, 2015, at 10:29 AM, Slawa Olhovchenkov wrote: > > On Tue, Oct 06, 2015 at 10:18:11AM -0500, 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 int

Re: Dell NVMe issues

2015-10-06 Thread Slawa Olhovchenkov
On Tue, Oct 06, 2015 at 10:18:11AM -0500, 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?i

Dell NVMe issues

2015-10-06 Thread Sean Kelly
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 .