On Tue, Sep 25, 2007 at 06:09:04PM -0700, Richard Elling wrote:
Actually, you can use the existing name space for this. By default,
ZFS uses /dev/dsk. But everything in /dev is a symlink. So you could
setup your own space, say /dev/myknowndisks and use more descriptive
names. You might
Quick reset, Greg Shaw asked for a more descriptive output for zpool
status. I've already demonstrated how to do that. We also discussed
the difficulty in making a reliable name to physical location map
without involving humans.
continuing on...
A Darren Dunham wrote:
On Wed, Sep 26, 2007 at
ZFS should allow 31+NULL chars for a comment against each disk.
This would work well with the host name string (I assume is max_hostname
255+NULL)
If a disk fails it should report c6t4908029d0 failed comment from
disk, it should also remember the comment until reboot
This would be useful for
zdb?
Damon Atkins wrote:
ZFS should allow 31+NULL chars for a comment against each disk.
This would work well with the host name string (I assume is max_hostname
255+NULL)
If a disk fails it should report c6t4908029d0 failed comment from
disk, it should also remember the comment until
On Wed, Sep 26, 2007 at 11:36:57AM -0700, Richard Elling wrote:
AFAIK, VxVM still only expects one private region per disk. The private
region stores info on the configuration of the logical devices on the
disk, and its participation therein. ZFS places this data in the on-disk
format on
Hi. I'd like to request a feature be added to zfs. Currently, on
SAN attached disk, zpool shows up with a big WWN for the disk. If
ZFS (or the zpool command, in particular) had a text field for
arbitrary information, it would be possible to add something that
would indicate what LUN on
Gregory Shaw wrote:
Hi. I'd like to request a feature be added to zfs. Currently, on
SAN attached disk, zpool shows up with a big WWN for the disk. If
ZFS (or the zpool command, in particular) had a text field for
arbitrary information, it would be possible to add something that
James C. McPherson wrote:
Gregory Shaw wrote:
Hi. I'd like to request a feature be added to zfs. Currently, on
SAN attached disk, zpool shows up with a big WWN for the disk. If
ZFS (or the zpool command, in particular) had a text field for
arbitrary information, it would be
Tim Spriggs wrote:
James C. McPherson wrote:
Gregory Shaw wrote:
...
The above would be very useful should a disk fail to identify what
device is what.
How would you gather that information?
How would you ensure that it stayed accurate in
a hotplug world?
If it is stored on the device
On Wed, 2007-09-26 at 08:26 +1000, James C. McPherson wrote:
How would you gather that information?
the tools to use would be dependant on the actual storage device in use.
luxadm for A5x00 and V8x0 internal storage, sccli for 3xxx, etc., etc.,
How would you ensure that it stayed accurate in
Bill Sommerfeld wrote:
On Wed, 2007-09-26 at 08:26 +1000, James C. McPherson wrote:
How would you gather that information?
the tools to use would be dependant on the actual storage device in use.
luxadm for A5x00 and V8x0 internal storage, sccli for 3xxx, etc., etc.,
No consistent
It would be a manual process. As with any arbitrary name, it's a useful
tag, not much more.
James C. McPherson wrote:
Gregory Shaw wrote:
Hi. I'd like to request a feature be added to zfs. Currently, on
SAN attached disk, zpool shows up with a big WWN for the disk. If
ZFS (or
James C. McPherson wrote:
Bill Sommerfeld wrote:
On Wed, 2007-09-26 at 08:26 +1000, James C. McPherson wrote:
How would you gather that information?
the tools to use would be dependant on the actual storage device in use.
luxadm for A5x00 and V8x0 internal storage, sccli
Greg Shaw wrote:
James C. McPherson wrote:
Bill Sommerfeld wrote:
On Wed, 2007-09-26 at 08:26 +1000, James C. McPherson wrote:
How would you gather that information?
the tools to use would be dependant on the actual storage device in use.
luxadm for A5x00 and V8x0 internal
Dale Ghent wrote:
On Sep 25, 2007, at 7:48 PM, Richard Elling wrote:
The problem with this is that wrong information is much worse than no
information, there is no way to automatically validate the
information,
and therefore people are involved. If people were reliable, then even
a text
On Sep 25, 2007, at 7:09 PM, Richard Elling wrote:
Dale Ghent wrote:
On Sep 25, 2007, at 7:48 PM, Richard Elling wrote:
The problem with this is that wrong information is much worse
than no
information, there is no way to automatically validate the
information,
and therefore people are
On 9/25/07, Gregory Shaw [EMAIL PROTECTED] wrote:
On Sep 25, 2007, at 7:09 PM, Richard Elling wrote:
Dale Ghent wrote:
On Sep 25, 2007, at 7:48 PM, Richard Elling wrote:
The problem with this is that wrong information is much worse than no
information, there is no way to automatically
Please don't do this as a rule, it makes for horrendous support issues
and breaks a lot of health check tools.
Actually, you can use the existing name space for this. By default,
ZFS uses /dev/dsk. But everything in /dev is a symlink. So you could
setup your own space, say
18 matches
Mail list logo
