From: NeilBrown <neilb@suse.com>
To: Nix <nix@esperi.org.uk>, linux-raid@vger.kernel.org
Subject: Re: mdadm --misc --readonly -> ENODEV indefinitely
Date: Mon, 29 May 2017 06:20:35 +1000 [thread overview]
Message-ID: <877f10hgx8.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <87y3th2rdu.fsf@esperi.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]
On Sun, May 28 2017, Nix wrote:
> So I was trying to flip on the RAID journal now I'd fully populated my
> array and cut over to it. So, from early userspace, I did
>
> # first line done by initramfs scripting
> /sbin/mdadm --assemble --scan --auto=md --freeze-reshape
> mdadm --misc --readonly /dev/md/fast
> mdadm --manage /dev/md/fast --add-journal /dev/ssd1
> mdadm --misc --readwrite /dev/md/fast
>
> This did not work as planned, or indeed at all. After the first
> --readonly, all requests for /dev/md/fast report "No such device or
> address" until a reboot, though /proc/mdstat says the thing is still
> there and /sys/block/md125/dev reports no change in major/minor numbers.
> (I don't have udev in my early-userspace environment, but mdev reports
> no change, either.)
>
> It's a bit hard to do anything else after that, like, say, turn the
> journal on.
>
> ... maybe an mdadm --assemble --scan --auto=md --readonly in one go
> would work better, rather than starting with the default (?read-mostly?)
> and flipping it? I'll give that a try later.
> --
> 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
Commit: 065e519e71b2 ("md: MD_CLOSING needs to be cleared after called md_set_readonly or do_md_stop")
Broken in v4.9-rc1
Fixed in v4.12-rc1
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-05-28 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 10:43 mdadm --misc --readonly -> ENODEV indefinitely Nix
2017-05-28 20:20 ` NeilBrown [this message]
2017-05-29 12:20 ` Nix
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=877f10hgx8.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=linux-raid@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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).