From owner-freebsd-bugs@freebsd.org  Fri Nov 27 11:07:14 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
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 0DC69A39956
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Fri, 27 Nov 2015 11:07:14 +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 EAA4B12A1
 for <freebsd-bugs@FreeBSD.org>; Fri, 27 Nov 2015 11:07:13 +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 tARB7DRY070675
 for <freebsd-bugs@FreeBSD.org>; Fri, 27 Nov 2015 11:07:13 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 186000] zdb(8): zdb -S poolname no longer works
Date: Fri, 27 Nov 2015 11:07:13 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: gert@greenie.muc.de
X-Bugzilla-Status: In Progress
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-186000-8-9Mu5RFlFPc@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-186000-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-186000-8@https.bugs.freebsd.org/bugzilla/>
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.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Nov 2015 11:07:14 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186000

--- Comment #2 from Gert Doering <gert@greenie.muc.de> ---
ok, turns out I could solve this on my own, so maybe the result can help either
make the tools more useful, or just fix the issue.

Turns out that when this pool was created, it was put on
/dev/multipath/fc_mpath (because there are two FC paths to the same LUN on a
SAN).  I made a mistake when creating the multipath label, that is, I only
"gmultipath create"'d it, not "gmultipath label" - it was in RAM, everything
worked, after reboot, the label was not there and the pool was imported from
/dev/da2.

And here comes's the catch: "zdb -s" still wanted to access
/dev/multipath/fc_mpath, which, of course, did not exist.

After fixing the labeling and re-importing the pool it works now.

But it's still a bug - at least, it should point out *what* is "No such file or
directory", or preferrably, just use the device that "zpool status" knows is
used...

-- 
You are receiving this mail because:
You are the assignee for the bug.