On 11/28/2015 01:19 AM, Christoph Anton Mitterer wrote:
On Fri, 2015-11-27 at 17:16 +0800, Anand Jain wrote:
I understand as a user, a full md/lvm set of features are important
to begin operations using btrfs and we don't have it yet. I have to
blame it on the priority list.
What's would be especially nice from the admin side, would be something
like /proc/mdstat, which centrally gives information about the health
of your RAID.
Yep. Its planned. A design doc was in my draft for some time now, I
just sent it to the mailing list for review comments.
It can/should of course be more than just "OK" / "not OK"...
information about which devices are in which state, whether a
rebuild/reconstruction/scrub is going on, etc. pp.
right.
Maybe even details of properties like chunk sizes (as far as these
apply to btrfs).
Having a dedicated monitoring process... well nice to have, but
something like mdstat is, always there, doesn't need special userland
tools and can easily used by 3rd party stuff like Icinga/Nagios
check_raid.
yep. will consider.
I think the keywords here are human readable + parseable... so maybe
even two files.
yeah. for parseable reasons I liked procs, there is experimental
/proc/fs/btrfs/devlist. but procs is kind of not recommended. So
probably we would need a wrapper tool on top the sysfs to provide
the same effect.
Thanks, Anand
Cheers,
Chris.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
