zpool status should show GUIDs #2011
Labels
Type: Feature
Feature request or new feature
Comments
|
#2012 closes this. |
ryao
added a commit
to ryao/zfs
that referenced
this issue
Dec 29, 2013
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands make the use of vdev GUIDs necessary. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to zpool_vdev_name, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
ryao
added a commit
to ryao/zfs
that referenced
this issue
Dec 29, 2013
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands make the use of vdev GUIDs necessary. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to zpool_vdev_name, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
ryao
added a commit
to ryao/zfs
that referenced
this issue
Dec 29, 2013
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands make the use of vdev GUIDs necessary. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
ryao
added a commit
to ryao/zfs
that referenced
this issue
Dec 29, 2013
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Jun 14, 2014
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Jul 23, 2014
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Sep 18, 2014
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
ryao
added a commit
to ryao/zfs
that referenced
this issue
Sep 30, 2014
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
ryao
added a commit
to ryao/zfs
that referenced
this issue
Sep 30, 2014
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
ryao
added a commit
to ryao/zfs
that referenced
this issue
Sep 30, 2014
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Oct 3, 2014
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
ryao
added a commit
to ryao/zfs
that referenced
this issue
Oct 8, 2014
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Nov 1, 2014
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Nov 14, 2014
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
ryao
added a commit
to openzfsonosx/zfs
that referenced
this issue
Nov 28, 2014
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs/zfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs/zfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org> (cherry picked from commit 9ef11fcd4ecf05a9ebe2cf9c65be4dd32cb6944f) Signed-off-by: ilovezfs <ilovezfs@icloud.com>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Jan 13, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Jan 14, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Feb 3, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Feb 12, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
kernelOfTruth
pushed a commit
to kernelOfTruth/zfs
that referenced
this issue
Feb 14, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by zpool status are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to zpool_vdev_name, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao ryao@gentoo.org
kernelOfTruth
pushed a commit
to kernelOfTruth/zfs
that referenced
this issue
Feb 18, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by zpool status are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to zpool_vdev_name, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao ryao@gentoo.org
kernelOfTruth
pushed a commit
to kernelOfTruth/zfs
that referenced
this issue
Mar 3, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by zpool status are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to zpool_vdev_name, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao ryao@gentoo.org
kernelOfTruth
pushed a commit
to kernelOfTruth/zfs
that referenced
this issue
Mar 13, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by zpool status are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to zpool_vdev_name, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao ryao@gentoo.org
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Apr 1, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Apr 4, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org> Signed-off-by: DHE <git@dehacked.net>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Apr 5, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Apr 5, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org> Signed-off-by: DHE <git@dehacked.net>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Apr 10, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Apr 21, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
kernelOfTruth
pushed a commit
to kernelOfTruth/zfs
that referenced
this issue
Apr 30, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
May 16, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
May 17, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
May 18, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
May 21, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
May 22, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
May 25, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Sep 17, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Oct 4, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Oct 5, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Oct 15, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Dec 7, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Dec 13, 2015
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Jan 29, 2016
The use of vdev GUIDs are a necessary workaround in edge cases where the names provided by `zpool status` are not accepted by the zpool detach/offline/remove/replace commands. The current method of obtaining them uses zdb, but this does not work in all cases (see openzfs#1530). This provides a method of obtaining vdev GUIDs that is more reliable and straightforward than zdb. It would be better to fix all edge cases that require the use of GUIDs as a workaround, but Linux's /dev design makes it difficult to anticipate such edge cases, which makes this option necessary. Note that this adds a new boolean parameter to `zpool_vdev_name`, which changes the libzfs interface. Closes openzfs#2011 Signed-off-by: Richard Yao <ryao@gentoo.org>
behlendorf
pushed a commit
to behlendorf/zfs
that referenced
this issue
Feb 18, 2016
The following options have been added to the zpool add, iostat,
list, status, and split subcommands. The default behavior was
not modified, from zfs(8).
-g Display vdev GUIDs instead of the normal short
device names. These GUIDs can be used in-place of
device names for the zpool detach/off‐
line/remove/replace commands.
-L Display real paths for vdevs resolving all symbolic
links. This can be used to lookup the current block
device name regardless of the /dev/disk/ path used
to open it.
-p Display full paths for vdevs instead of only the
last component of the path. This can be used in
conjunction with the -L flag.
This change is based on worked originally started by Richard Yao
to add a -g option. Then extended by @ilovezfs to add a -L option
for openzfsonosx. Those changes have been merged, re-factored,
a -p option added and extended to all relevant zpool subcommands.
Original-patch-by: Richard Yao <ryao@gentoo.org>
Extended-by: ilovezfs <ilovezfs@icloud.com>
Extended-by: Brian Behlendorf <behlendorf1@llnl.gov>
Issue openzfs#2011
Issue openzfs#4341
behlendorf
pushed a commit
to behlendorf/zfs
that referenced
this issue
Feb 18, 2016
The following options have been added to the zpool add, iostat,
list, status, and split subcommands. The default behavior was
not modified, from zfs(8).
-g Display vdev GUIDs instead of the normal short
device names. These GUIDs can be used in-place of
device names for the zpool detach/off‐
line/remove/replace commands.
-L Display real paths for vdevs resolving all symbolic
links. This can be used to lookup the current block
device name regardless of the /dev/disk/ path used
to open it.
-p Display full paths for vdevs instead of only the
last component of the path. This can be used in
conjunction with the -L flag.
This behavior may also be enabled using the following environment
variables.
ZPOOL_VDEV_NAME_GUID
ZPOOL_VDEV_NAME_FOLLOW_LINKS
ZPOOL_VDEV_NAME_PATH
This change is based on worked originally started by Richard Yao
to add a -g option. Then extended by @ilovezfs to add a -L option
for openzfsonosx. Those changes have been merged, re-factored,
a -p option added and extended to all relevant zpool subcommands.
Original-patch-by: Richard Yao <ryao@gentoo.org>
Extended-by: ilovezfs <ilovezfs@icloud.com>
Extended-by: Brian Behlendorf <behlendorf1@llnl.gov>
Issue openzfs#2011
Issue openzfs#4341
behlendorf
pushed a commit
to behlendorf/zfs
that referenced
this issue
Feb 18, 2016
The following options have been added to the zpool add, iostat,
list, status, and split subcommands. The default behavior was
not modified, from zfs(8).
-g Display vdev GUIDs instead of the normal short
device names. These GUIDs can be used in-place of
device names for the zpool detach/off‐
line/remove/replace commands.
-L Display real paths for vdevs resolving all symbolic
links. This can be used to lookup the current block
device name regardless of the /dev/disk/ path used
to open it.
-p Display full paths for vdevs instead of only the
last component of the path. This can be used in
conjunction with the -L flag.
This behavior may also be enabled using the following environment
variables.
ZPOOL_VDEV_NAME_GUID
ZPOOL_VDEV_NAME_FOLLOW_LINKS
ZPOOL_VDEV_NAME_PATH
This change is based on worked originally started by Richard Yao
to add a -g option. Then extended by @ilovezfs to add a -L option
for openzfsonosx. Those changes have been merged, re-factored,
a -p option added and extended to all relevant zpool subcommands.
Original-patch-by: Richard Yao <ryao@gentoo.org>
Extended-by: ilovezfs <ilovezfs@icloud.com>
Extended-by: Brian Behlendorf <behlendorf1@llnl.gov>
Issue openzfs#2011
Issue openzfs#4341
nedbass
pushed a commit
that referenced
this issue
Mar 23, 2016
The following options have been added to the zpool add, iostat,
list, status, and split subcommands. The default behavior was
not modified, from zfs(8).
-g Display vdev GUIDs instead of the normal short
device names. These GUIDs can be used in-place of
device names for the zpool detach/off‐
line/remove/replace commands.
-L Display real paths for vdevs resolving all symbolic
links. This can be used to lookup the current block
device name regardless of the /dev/disk/ path used
to open it.
-p Display full paths for vdevs instead of only the
last component of the path. This can be used in
conjunction with the -L flag.
This behavior may also be enabled using the following environment
variables.
ZPOOL_VDEV_NAME_GUID
ZPOOL_VDEV_NAME_FOLLOW_LINKS
ZPOOL_VDEV_NAME_PATH
This change is based on worked originally started by Richard Yao
to add a -g option. Then extended by @ilovezfs to add a -L option
for openzfsonosx. Those changes have been merged, re-factored,
a -p option added and extended to all relevant zpool subcommands.
Original-patch-by: Richard Yao <ryao@gentoo.org>
Extended-by: ilovezfs <ilovezfs@icloud.com>
Extended-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: ilovezfs <ilovezfs@icloud.com>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #2011
Closes #4341
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice if zpool status would show disk GUIDs via a -g flag possibly.
The text was updated successfully, but these errors were encountered: