From: Phil Turmel <philip@turmel.org>
To: Adam Goryachev <mailinglists@websitemanagers.com.au>,
Anugraha Sinha <asinha.mailinglist@gmail.com>,
linux-raid@vger.kernel.org
Subject: Re: Converting 4 disk RAID10 to RAID5
Date: Wed, 28 Oct 2015 09:56:10 -0400 [thread overview]
Message-ID: <5630D3FA.70305@turmel.org> (raw)
In-Reply-To: <56302B95.3000006@websitemanagers.com.au>
On 10/27/2015 09:57 PM, Adam Goryachev wrote:
>
> Any final comments/suggestions before I start the process "for real"?
Do a 'check' scrub before the raid10 to raid0 conversion.
Great report!
Phil
prev parent reply other threads:[~2015-10-28 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 1:26 Converting 4 disk RAID10 to RAID5 Adam Goryachev
2015-10-26 14:09 ` Anugraha Sinha
2015-10-26 14:10 ` Phil Turmel
2015-10-26 23:55 ` Adam Goryachev
2015-10-27 6:19 ` Anugraha Sinha
2015-10-27 6:32 ` Adam Goryachev
2015-10-27 12:13 ` Phil Turmel
2015-10-28 1:57 ` Adam Goryachev
2015-10-28 13:56 ` Phil Turmel [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=5630D3FA.70305@turmel.org \
--to=philip@turmel.org \
--cc=asinha.mailinglist@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.au \
/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).