From: "Francois Billard" <francois.billard@alyseo.com>
To: 'NeilBrown' <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: RE: Managing mdam
Date: Wed, 11 Sep 2013 09:40:23 +0200 [thread overview]
Message-ID: <026e01ceaec2$2ced7110$86c85330$@alyseo.com> (raw)
In-Reply-To: <20130911094848.00289146@notabene.brown>
We want to embed raid management in our application. But we want a better
solution if it exists rather than parsing the output of mdadm which is error
prone.
Is there a solution or should i write kilometer of regexp ? :)
-----Message d'origine-----
De : linux-raid-owner@vger.kernel.org
[mailto:linux-raid-owner@vger.kernel.org] De la part de NeilBrown
Envoyé : mercredi 11 septembre 2013 01:49
À : Francois Billard
Cc : linux-raid@vger.kernel.org
Objet : Re: Managing mdam
On Tue, 10 Sep 2013 10:03:23 +0200 Francois Billard
<francois.billard@alyseo.com> wrote:
> Hi,
>
> Is it possible to manage mdadm from an external point of view ? with a
> library with bindings in some language (Python) for example ?
> Thanks in advance
>
> Regards,
> Francois
Only by running mdadm in a separate process and passing appropriate
arguments.
Is there something particular that you wanted to do?
NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-09-11 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 5:00 Subject: [PATCH] md: avoid deadlock when raid5 array has unack badblocks during md_stop_writes y b
2013-09-10 5:33 ` NeilBrown
2013-09-10 7:19 ` y b
2013-09-10 8:03 ` Managing mdam Francois Billard
2013-09-10 23:48 ` NeilBrown
2013-09-11 7:40 ` Francois Billard [this message]
2013-09-11 8:37 ` NeilBrown
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='026e01ceaec2$2ced7110$86c85330$@alyseo.com' \
--to=francois.billard@alyseo.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).