From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Adam Goryachev <mailinglists@websitemanagers.com.au>
Cc: Song Liu <songliubraving@fb.com>,
linux-raid@vger.kernel.org, yizhan@redhat.com,
Shaohua Li <shli@fb.com>
Subject: Re: [PATCH] mdadm: add man page for --add-journal
Date: Mon, 15 Aug 2016 10:42:30 -0400 [thread overview]
Message-ID: <wrfj60r25c15.fsf@redhat.com> (raw)
In-Reply-To: <defa4365-a771-f4e8-4375-b67bc933767b@websitemanagers.com.au> (Adam Goryachev's message of "Sat, 13 Aug 2016 15:13:47 +1000")
Adam Goryachev <mailinglists@websitemanagers.com.au> writes:
> On 13/08/2016 00:58, Jes Sorensen wrote:
>> Song Liu <songliubraving@fb.com> writes:
>>> Add the following to man page:
>>>
>>> --add-journal
>>> Recreate journal for RAID-4/5/6 array that losts journal
>>> devices. In current implementation, this command cannot
>>> add journal to an array that had failed journal. To
>>> avoid interrupting on-going write opertions,
>>> --add-journal only works for array in Read-Only state.
>>>
>>> Reported-by: Yi Zhang <yizhan@redhat.com>
>>> Signed-off-by: Song Liu <songliubraving@fb.com>
>>> Signed-off-by: Shaohua Li <shli@fb.com>
>>> ---
>>> mdadm.8.in | 8 ++++++++
>>> 1 file changed, 8 insertions(+)
>> Applied, with a few minor mods.
>>
>> I changed it to say this, I hope you are fine with that:
>>
>> "Recreate journal for RAID-4/5/6 array that lost a journal device. In the
>> current implementation, this command cannot add a journal to an array
>> that had a failed journal. To avoid interrupting on-going write
>> opertions, "
> I think this might be more correct:
>
> "Recreate journal for RAID-4/5/6 array that lost a journal device. In the
> current implementation, this command cannot add a journal to an array
> that *has* a failed journal. To avoid interrupting on-going write
> *operations*, "
>
>
> Note the two words modified have **
> has mean currently, if it had (past) a failed journal, but that has
> already been fixed, then it currently has a working journal, and so I
> assume this patch is not relevant. It's only related to if the array
> is currently missing a journal...
> The second operations is just a typo...
>
> Hope you don't mind my jumping in here, I can't help much with code,
> but hopefully contribution is still helpful.
If Song is happy with this and you send me a patch, I'll be happy to
apply it.
Cheers,
Jes
next prev parent reply other threads:[~2016-08-15 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 0:10 [PATCH] mdadm: add man page for --add-journal Song Liu
2016-08-12 14:58 ` Jes Sorensen
2016-08-13 5:13 ` Adam Goryachev
2016-08-15 14:42 ` Jes Sorensen [this message]
2016-08-15 17:16 ` Song Liu
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=wrfj60r25c15.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.au \
--cc=shli@fb.com \
--cc=songliubraving@fb.com \
--cc=yizhan@redhat.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