Date: Mon, 1 Aug 2016 16:38:18 +0200 From: Borja Marcos <borjam@sarenet.es> To: Jim Harris <jim.harris@gmail.com> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Intel NVMe troubles? Message-ID: <4996AF96-76BA-47F1-B328-D4FE7AC777EE@sarenet.es> In-Reply-To: <CAJP=Hc-3ogfoSZ0cjycm%2Bsb0M80B6M5ZrGtWn1BjfOFPteGgdA@mail.gmail.com> References: <CBC304D0-AA57-4EF5-A2DD-1888FB88DE12@sarenet.es> <CAJP=Hc-KdmScZtCRDcF=CTpNcMkn2brXiPx4XwJA0aTYgkxm%2Bg@mail.gmail.com> <AAC8E93B-F263-4B7E-91DF-9EAC77FB2C3C@sarenet.es> <CAJP=Hc-3ogfoSZ0cjycm%2Bsb0M80B6M5ZrGtWn1BjfOFPteGgdA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 29 Jul 2016, at 17:44, Jim Harris <jim.harris@gmail.com> wrote: >=20 >=20 >=20 > On Fri, Jul 29, 2016 at 1:10 AM, Borja Marcos <borjam@sarenet.es> = wrote: >=20 > > On 28 Jul 2016, at 19:25, Jim Harris <jim.harris@gmail.com> wrote: > > > > Yes, you should worry. > > > > Normally we could use the dump_debug sysctls to help debug this - = these > > sysctls will dump the NVMe I/O submission and completion queues. = But in > > this case the LBA data is in the payload, not the NVMe submission = entries, > > so dump_debug will not help as much as dumping the NVMe DSM payload > > directly. > > > > Could you try the attached patch and send output after recreating = your pool? >=20 > Just in case the evil anti-spam ate my answer, sent the results to = your Gmail account. >=20 >=20 > Thanks Borja. >=20 > It looks like all of the TRIM commands are formatted properly. The = failures do not happen until about 10 seconds after the last TRIM to = each drive was submitted, and immediately before TRIMs start to the next = drive, so I'm assuming the failures are for the the last few TRIM = commands but cannot say for sure. Could you apply patch v2 (attached) = which will dump the TRIM payload contents inline with the failure = messages? Sure, this is the complete /var/log/messages starting with the system = boot. Before booting I destroyed the pool so that you could capture what happens when booting, zpool create, etc. Remember that the drives are in LBA format #3 (4 KB blocks). As far as I = know that=E2=80=99s preferred to the old 512 byte blocks. Thank you very much and sorry about the belated response. Borja.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4996AF96-76BA-47F1-B328-D4FE7AC777EE>