From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Joel Parthemore <joel@parthemores.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: request for help on IMSM-metadata RAID-5 array
Date: Mon, 25 Sep 2023 18:43:14 +0200 [thread overview]
Message-ID: <20230925184314.00005d58@linux.intel.com> (raw)
In-Reply-To: <e8fbc585-9367-a865-8c18-bf9e4fc7562f@parthemores.com>
On Mon, 25 Sep 2023 17:52:41 +0200
Joel Parthemore <joel@parthemores.com> wrote:
> Den 2023-09-25 kl. 11:44, skrev Mariusz Tkaczyk:
>
> > Hi Joel,
> > sorry for late response, I see that you were able to recover the data!
>
>
> Yes. I just wanted to proceed as slowly and carefully as possible so
> that I would not make an awkward situation worse. ;-) The advice I got
> from the list gave me the assurance to go ahead.
>
>
> > I think that metadata manager is down or broken from some reasons.
> > #systemctl status mdmon@md127.service
>
>
> I forgot to say with my earlier post that I'm not running systemd but
> rather openrc. Gentoo supports both, and I have my reasons for
> preferring not to make the switch to systemd. Therefore...
>
>
> > I you will get the problem again, please try (but do not abuse- use it as
> > last resort!!):
> > #systemctl restart mdmon@md127.service
>
>
> ...That solution won't work. ;-)
>
> If I do have the problem again, maybe I can come to understand better
> how/why it's happening.
>
Ohh, ok. Please note that VROC solution is not validated with openrc and we
have userspace metadata manager, it requires to be careful even with systemd.
In this case native metadata is safer option because the metadata management is
done by kernel. But... you used this for years with no issues so I seems to be
not so bad. Anyway you can always try # mdmon -at to gentle ask metadata daemon
to fork and restart for every IMSM array in your system.
Mariusz
prev parent reply other threads:[~2023-09-25 16:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 10:54 request for help on IMSM-metadata RAID-5 array Joel Parthemore
2023-09-23 11:24 ` Roman Mamedov
2023-09-23 15:18 ` Joel Parthemore
2023-09-23 15:35 ` Roman Mamedov
2023-09-23 15:45 ` Joel Parthemore
2023-09-23 18:49 ` Joel Parthemore
2023-09-25 1:43 ` Yu Kuai
2023-09-25 15:57 ` Joel Parthemore
2023-09-26 1:10 ` Yu Kuai
2023-09-29 19:44 ` Joel Parthemore
[not found] ` <a0b8a693-5d9c-d354-5afc-4500b78a983e@huaweicloud.com>
2023-10-05 7:28 ` Joel Parthemore
2023-09-25 9:44 ` Mariusz Tkaczyk
2023-09-25 15:52 ` Joel Parthemore
2023-09-25 16:43 ` Mariusz Tkaczyk [this message]
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=20230925184314.00005d58@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=joel@parthemores.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