From: Wols Lists <antlists@youngman.org.uk>
To: Reindl Harald <h.reindl@thelounge.net>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: RAID header in XFS area?
Date: Sat, 4 Nov 2017 21:54:06 +0000 [thread overview]
Message-ID: <59FE36FE.4070705@youngman.org.uk> (raw)
In-Reply-To: <df1cda5a-57c3-7f9a-2f93-54ef01c19a30@thelounge.net>
On 04/11/17 20:36, Reindl Harald wrote:
>>
>> While the system is RUNNING, yes. But if the array is STOPPED, mdadm
>> will refuse to start it. At least, that's certainly how I understand
>> it works ...
>>
>> Do you REALLY want the system to be running, and give you no clue that
>> it's not working properly?
>
> mdmon typically writes a mail about a degraded array - so far away from
> "no clue"
mdmon? What's that? Yes, I know, it's the monitor. But how do you know
whether or not it's running? It certainly isn't on my system.
Anyways, as I said, as far as I am aware, "mdadm --run" does NOT work on
a degraded array unless either the previous --run was on a degraded
array, or you use --force.
Which means if you remove a disk from an array, and then try to restart
the array, the restart will fail. Which is exactly the OP's scenario.
Cheers,
Wol
next prev parent reply other threads:[~2017-11-04 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 18:10 RAID header in XFS area? David F.
2017-11-04 18:30 ` Wols Lists
2017-11-04 18:34 ` Reindl Harald
2017-11-04 19:27 ` Wol's lists
2017-11-04 20:36 ` Reindl Harald
2017-11-04 21:54 ` Wols Lists [this message]
2017-11-05 3:34 ` Reindl Harald
2017-11-06 21:31 ` Phil Turmel
[not found] ` <CAGRSmLuoauKaSZ5Z73+Tg19e_1q9Tc-A0ZjqMgr4Lv9Tfer6QQ@mail.gmail.com>
2017-11-04 22:55 ` Wol's lists
[not found] ` <CAGRSmLvou+yEb2VLJoounbuiEdfrPSEC+8xBtdp9nfOpj8y-8Q@mail.gmail.com>
[not found] ` <CAGRSmLuBEUynKNirFi9FuoJz82F4hDimmJWZSSfpQhoOi_9Rog@mail.gmail.com>
2017-11-05 2:12 ` David F.
2017-11-05 9:16 ` Wols Lists
2017-11-05 15:59 ` David F.
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=59FE36FE.4070705@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=h.reindl@thelounge.net \
--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).