From owner-freebsd-bugs@freebsd.org Tue Jul 26 21:08:36 2016 Return-Path: Delivered-To: freebsd-bugs@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 506C7BA4F29 for ; Tue, 26 Jul 2016 21:08:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 272971C14 for ; Tue, 26 Jul 2016 21:08:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u6QL8Z9Q023278 for ; Tue, 26 Jul 2016 21:08:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 211381] L2ARC degraded, repeatedly, on Samsung SSD 950 Pro nvme Date: Tue, 26 Jul 2016 21:08:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: braddeicide@hotmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2016 21:08:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211381 --- Comment #4 from braddeicide@hotmail.com --- Yes I was suspicious of the script when I removed and readded the device an= d it worked for a while, but the script kept saying degraded. How I can tell it= 's gone wrong again however is in zpool iostat -v when all data is dropped from the arc and capacity stays 100% free despite writes. # dtrace -n 'sdt:::l2arc-iodone /args[0]->io_error !=3D 0/ { printf("io_err= or =3D %d", args[0]->io_error); }' dtrace: description 'sdt:::l2arc-iodone ' matched 1 probe dtrace: buffer size lowered to 512k CPU ID FUNCTION:NAME 0 57400 none:l2arc-iodone io_error =3D 22 3 57400 none:l2arc-iodone io_error =3D 22 1 57400 none:l2arc-iodone io_error =3D 22 1 57400 none:l2arc-iodone io_error =3D 22 1 57400 none:l2arc-iodone io_error =3D 22 3 57400 none:l2arc-iodone io_error =3D 22 3 57400 none:l2arc-iodone io_error =3D 22 3 57400 none:l2arc-iodone io_error =3D 22 1 57400 none:l2arc-iodone io_error =3D 22 3 57400 none:l2arc-iodone io_error =3D 22 0 57400 none:l2arc-iodone io_error =3D 22 1 57400 none:l2arc-iodone io_error =3D 22 0 57400 none:l2arc-iodone io_error =3D 22 2 57400 none:l2arc-iodone io_error =3D 22 --=20 You are receiving this mail because: You are the assignee for the bug.=