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
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 unt
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
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
On Wed, Sep 26, 2007 at 09:53:00AM -0700, Richard Elling wrote:
> A Darren Dunham wrote:
> >It seems to me that would limit the knowledge to the currently imported
> >machine, not keep it with the pool.
>
> The point is that the name of the vdev doesn't really matter to ZFS.
I would assume the
A Darren Dunham wrote:
> 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 desc
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
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 /dev/mykno
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 automat
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 in
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 eve
On Sep 25, 2007, at 5:48 PM, Richard Elling wrote:
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 u
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 file would wo
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
On Sep 25, 2007, at 7:21 PM, James C. McPherson wrote:
>
> That sounds like an ok RFE to me.
>
> For some of the arrays (eg HDS) that we come
> into contact with, it's possible to decode the
> device guid into something meaningful to a
> human, but that's generally closed information.
To me, this
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 A5
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 s
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
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 int
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
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 o
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 woul
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
23 matches
Mail list logo
