[Bug 186000] zdb(8): zdb -S poolname no longer works

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Nov 27 11:07:14 UTC 2015


--- Comment #2 from Gert Doering <gert at 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

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

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

More information about the freebsd-bugs mailing list