From: Larkin Lowrey <llowrey@gmail.com>
To: Song Liu <songliubraving@fb.com>, linux-raid@vger.kernel.org
Cc: shli@kernel.org, jes.sorensen@gmail.com
Subject: Re: [PATCH 2/2] mdadm: remove journal with "remove-journal"
Date: Thu, 16 Nov 2017 12:35:06 -0500 [thread overview]
Message-ID: <24a446c5-18bd-bcfe-02a4-ec569dc572a5@gmail.com> (raw)
In-Reply-To: <20170831175101.2965834-1-songliubraving@fb.com>
Is it not possible to permanently remove a journal and return to resync
mode?
Here's what I tried:
# mdadm --readonly /dev/md124
# cat /proc/mdstat
Personalities : [raid10] [raid0] [raid6] [raid5] [raid4]
md124 : active (read-only) raid5 md123[7] md127p4[15](J) sdp1[13]
sdl1[10] sdg1[12] sdf1[11] sdo1[14] sdj1[8] sdq1[9] md122[6]
62509129728 blocks super 1.2 level 5, 512k chunk, algorithm 2
[9/9] [UUUUUUUUU]
# mdadm /dev/md124 --fail /dev/md127p4
mdadm: set /dev/md127p4 faulty in /dev/md124
# mdadm /dev/md124 --remove /dev/md127p4
mdadm: hot removed /dev/md127p4 from /dev/md124
# cat /sys/block/md124/md/consistency_policy
journal
# echo resync > /sys/block/md124/md/consistency_policy
# cat /sys/block/md124/md/consistency_policy
resync
# mdadm --stop /dev/md124
mdadm: stopped /dev/md124
# mdadm --assemble /dev/md124 /dev/md12[23] /dev/sd[goqpjfl]1
mdadm: Not safe to assemble with missing or stale journal device,
consider --force.
--Larkin
On 8/31/2017 1:51 PM, Song Liu wrote:
> Hi Larkin,
>
> We didn't ship this patch. Instead, we decide to use sysfs entry
>
> /sys/block/mdXXX/md/consistency_policy
>
> You can find the patch at:
>
> https://marc.info/?l=linux-raid&m=149063896208043
>
> Thanks,
> Song
> --
> 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:[~2017-11-16 17:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 15:54 [PATCH 2/2] mdadm: remove journal with "remove-journal" Larkin Lowrey
2017-08-31 17:51 ` Song Liu
2017-09-01 14:56 ` Larkin Lowrey
2017-11-16 17:35 ` Larkin Lowrey [this message]
2017-11-16 17:55 ` Song Liu
2017-11-20 16:04 ` Larkin Lowrey
-- strict thread matches above, loose matches on Subject: below --
2017-03-15 18:28 [PATCH 1/2] mdadm/r5cache: allow adding journal to array without journal Song Liu
2017-03-15 18:28 ` [PATCH 2/2] mdadm: remove journal with "remove-journal" Song Liu
2017-03-17 19:39 ` jes.sorensen
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=24a446c5-18bd-bcfe-02a4-ec569dc572a5@gmail.com \
--to=llowrey@gmail.com \
--cc=jes.sorensen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=shli@kernel.org \
--cc=songliubraving@fb.com \
/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).