From: Phil Turmel <philip@turmel.org>
To: maurice <mhilarius@gmail.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Looking for the best way to do this
Date: Thu, 23 Jun 2011 19:41:13 -0400 [thread overview]
Message-ID: <4E03CF19.1040702@turmel.org> (raw)
In-Reply-To: <4E03CBC3.1080001@gmail.com>
Hi Maurice,
[restored CC list.... use reply-to-all on kernel.org lists]
On 06/23/2011 07:26 PM, maurice wrote:
> On 6/23/2011 4:55 PM, Phil Turmel wrote:
>> Hi maurice,
>
> Hi Phil
>
> That was great, thank you!
>
> I gather that the R10 results ion a faster disk IO, in general?
> Probably with the "far" version, if we are mostly reading?
For most applications, yes. I haven't benchmarked it myself, though.
> I would be willing to lose redundancy for the duration of the creation process.
> Both disks presently seem to be OK.
You'll also be offline while copying and switching to the new filesystem. Did you want layout=f2 or =f3 ?
> Any chance you could "wrap up" for me with the correct syntax for this?
> I find that the "trial and error " approach is less than optimal.
First, run a check on your array, to minimize the chance of a read error during the copy:
echo "check" >/sys/block/md*/md/sync_action
While that's running, send me the output of "lsdrv", which will let me give advice with real device names:
wget -O /usr/sbin/lsdrv http://github.com/pturmel/lsdrv/raw/master/lsdrv ; chmod 755 /usr/sbin/lsdrv ; lsdrv
Phil
next prev parent reply other threads:[~2011-06-23 23:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 18:13 Looking for the best way to do this maurice
2011-06-23 1:20 ` Leslie Rhorer
2011-06-23 19:23 ` Iordan Iordanov
2011-06-23 22:06 ` maurice
2011-06-23 22:55 ` Phil Turmel
[not found] ` <4E03CBC3.1080001@gmail.com>
2011-06-23 23:41 ` Phil Turmel [this message]
2011-06-24 16:17 ` Iordan Iordanov
2011-06-24 16:35 ` maurice
2011-06-24 16:59 ` Iordan Iordanov
2011-06-24 17:11 ` maurice
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=4E03CF19.1040702@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mhilarius@gmail.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).