From owner-freebsd-bugs@FreeBSD.ORG Thu Jul 24 17:46:56 2014 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 47CC97AC for ; Thu, 24 Jul 2014 17:46:56 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 15BCF299B for ; Thu, 24 Jul 2014 17:46:56 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s6OHkt5S080471 for ; Thu, 24 Jul 2014 17:46:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 192097] New: zpool status -x reports wrong information Date: Thu, 24 Jul 2014 17:46:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: dustinwenz@ebureau.com X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.18 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2014 17:46:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192097 Bug ID: 192097 Summary: zpool status -x reports wrong information Product: Base System Version: 10.0-STABLE Hardware: Any OS: Any Status: Needs Triage Severity: Affects Many People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: dustinwenz@ebureau.com If a user has a pool created in FreeBSD 9.2 or earlier, it's likely that the ashift value is off. After upgrading to FreeBSD 10, zpool status correctly reports "block size: 512B configured, 4096B native". The problem is that when "zpool status -x" is run, it also reports the block size message. The documentation for -x states: "Only display status for pools that are exhibiting errors or are otherwise unavailable". While an ashift of 9 may not be ideal, it's a perfectly functional configuration and not an error. The new behavior is wrong because it presents many lines of messages, even when there are no degraded pools or data integrity errors. I personally find this annoying because I routinely check hundreds of pools for failing disks using the -x option, and it's easy to miss these errors when many pools have ashift=9. I'm already aware that the pools need to rebuilt to avoid that message, which is a process that will take years to complete. In the meantime, I still need to handle disk errors without being bombarded with redundant block size messages. -- You are receiving this mail because: You are the assignee for the bug.