Date: Fri, 29 Jul 2016 10:10:16 +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: <AAC8E93B-F263-4B7E-91DF-9EAC77FB2C3C@sarenet.es> In-Reply-To: <CAJP=Hc-KdmScZtCRDcF=CTpNcMkn2brXiPx4XwJA0aTYgkxm%2Bg@mail.gmail.com> References: <CBC304D0-AA57-4EF5-A2DD-1888FB88DE12@sarenet.es> <CAJP=Hc-KdmScZtCRDcF=CTpNcMkn2brXiPx4XwJA0aTYgkxm%2Bg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 28 Jul 2016, at 19:25, Jim Harris <jim.harris@gmail.com> wrote: >=20 > Yes, you should worry. >=20 > 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. >=20 > Could you try the attached patch and send output after recreating your = pool? Just in case the evil anti-spam ate my answer, sent the results to your = Gmail account. Borja.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AAC8E93B-F263-4B7E-91DF-9EAC77FB2C3C>