David Smith wrote:
> I was wondering if anyone had a script to parse the "zpool status -v" output
> into a more machine readable format?
>
> Thanks,
>
> David
>
>
> This message posted from opensolaris.org
> ___
> zfs-discuss mailing list
> zfs-discu
I was wondering if anyone had a script to parse the "zpool status -v" output
into a more machine readable format?
Thanks,
David
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolari
On Apr 19, 2007, at 12:50 PM, Ricardo Correia wrote:
eric kustarz wrote:
Two reasons:
1) cluttered the output (as the path name is variable length). We
could perhaps add another flag (-V or -vv or something) to display
the
ranges.
2) i wasn't convinced that output was useful, especially to
eric kustarz wrote:
> Two reasons:
> 1) cluttered the output (as the path name is variable length). We
> could perhaps add another flag (-V or -vv or something) to display the
> ranges.
> 2) i wasn't convinced that output was useful, especially to most
> users/admins.
>
> If we did provide the ran
On Apr 19, 2007, at 1:38 AM, Ricardo Correia wrote:
Why doesn't "zpool status -v" display the byte ranges of permanent
errors anymore, like it used to (before snv_57)?
I think it was a useful feature. For example, I have a pool with 17
permanent errors in 2 files with 700 MB each, but no abili
Why doesn't "zpool status -v" display the byte ranges of permanent
errors anymore, like it used to (before snv_57)?
I think it was a useful feature. For example, I have a pool with 17
permanent errors in 2 files with 700 MB each, but no ability to see
directly which one has the most errors or whic
