linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: xosview - anybody willing to test it (the raid features :-)
Date: Thu, 4 Aug 2016 23:27:35 +0100	[thread overview]
Message-ID: <57A3C157.100@youngman.org.uk> (raw)
In-Reply-To: <22435.38657.908865.828712@lrd.home.lan>

Mike has pushed a test version to sourceforge and github. If anybody's
willing to clone the repository, compile and test that would be appreciated.

For those who don't know this utility, once you've built it just do
"xosview &" at the command line and you'll get a pretty little status
monitor appear on your screen.

I'm planning to test it tomorrow (wife permitting), so I'm not sure how
it's going to behave myself. As Mike says, all feedback will be welcome.

Cheers,
Wol


-------- Forwarded Message --------

  This may help.  I've turned the raid meter on by default and it is set to
auto which causes it to search for and display a meter for every md
device it
finds.  The meter gives a pretty compact overview of the raids current state
in one glance.

  If you are able to checkout and build a copy of the source from either of
these two repositories (I push to both) I'd be interested in your feedback.

https://sourceforge.net/p/xosview/git/ci/master/tree/

https://github.com/mromberg/xosview

  I developed the new raid meter code using a few of raid1 devices
(two drives per raid) with a fedora 24 setup running on a VM.   But I am not
an experienced raid administrator by any stretch of the imagination.   I
have
no doubt that there are cases and configurations I have not tested or
accounted
for.  So, I welcome any feedback on what is there so far.

Mike






           reply	other threads:[~2016-08-04 22:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <22435.38657.908865.828712@lrd.home.lan>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57A3C157.100@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).