All of lore.kernel.org
 help / color / mirror / Atom feed
From: berk walker <berk@panix.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Neil Brown <neilb@suse.de>, Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Changing chunk size
Date: Sat, 17 Feb 2007 20:51:40 -0500	[thread overview]
Message-ID: <45D7B12C.4010109@panix.com> (raw)
In-Reply-To: <45D5E05E.4000706@tmr.com>



Bill Davidsen wrote:
> Neil Brown wrote:
>> On Thursday February 15, davidsen@tmr.com wrote:
>>  
>>> I have determined that a large array was created with an 
>>> overly-large chunk size. Best way to resize?
>>>     
>>
>> Dump and restore.
>>
>> in-place reshapes (such as raid5 + 1 disk => raid6 or
>> change-chunk-size) are on my list of 'that might be interesting to
>> implement', but there are plenty of more interesting things.  And it
>> would be very slow.  It would need to copy some number of stripes to a
>> backup somewhere, then copy them back in the new layout, so every
>> block in the array would be written twice.
> I'm sure "slow" is a relative term, compared to backing up TBs of data 
> and trying to restore them. Not to mention the lack of inexpensive TB 
> size backup media. That's totally unavailable at the moment, I'll live 
> with what I have, thanks.


> If you were to be a gambler, Bill - Get 2 disks big enough to store 
> your data, create a RAID5 mising one, and copy over the data.  Re do 
> the original array, and copy back.
Yeah, $0.02 doesn't buy much anymore.  Besides, you'll be needing bigger 
disks for the next machine you build,eh?

b-


  parent reply	other threads:[~2007-02-18  1:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 17:16 Changing chunk size Bill Davidsen
2007-02-15 23:24 ` Neil Brown
2007-02-16 16:48   ` Bill Davidsen
2007-02-16 18:49     ` Steve Cousins
2007-02-16 19:28       ` Justin Piszcz
2007-02-16 23:15         ` Bill Davidsen
2007-02-16 23:09       ` Bill Davidsen
2007-02-18  1:51     ` berk walker [this message]
2007-02-18 20:17       ` Bill Davidsen

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=45D7B12C.4010109@panix.com \
    --to=berk@panix.com \
    --cc=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.