From: Justin Capella <justincapella@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Fwd: mdadm: not rebuilding IMSM array without OROM
Date: Wed, 16 Sep 2015 10:54:44 -0700 [thread overview]
Message-ID: <CAMrEMU_du7HKa5x9dNpiBkp103-9NtF0fXD+Bv-Y6o41tEM85A@mail.gmail.com> (raw)
In-Reply-To: <CAMrEMU_LmmB-fmLkW1g6ptYnM-qbXNBJL58NR0Ok8Ecx_16KRA@mail.gmail.com>
In reference to the following commit:
http://git.neil.brown.name/?p=mdadm.git;a=commit;h=7eee461e91df702d8f588955b03e5bbb07e1f88d
I am unclear how to proceed given my unfortunate environment, where I
have replaced the motherboard. I am fearful of reconfiguring the raid
in OROM in case it causes data loss. Is anyone aware of a tool to
rebuild/configure the OROM settings from the autodetected ones?
Should I just modify my startup scripts in my initrd by hand to include --force?
next parent reply other threads:[~2015-09-16 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMrEMU_LmmB-fmLkW1g6ptYnM-qbXNBJL58NR0Ok8Ecx_16KRA@mail.gmail.com>
2015-09-16 17:54 ` Justin Capella [this message]
2015-09-17 8:43 ` Fwd: mdadm: not rebuilding IMSM array without OROM Artur Paszkiewicz
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=CAMrEMU_du7HKa5x9dNpiBkp103-9NtF0fXD+Bv-Y6o41tEM85A@mail.gmail.com \
--to=justincapella@gmail.com \
--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).