All of lore.kernel.org
 help / color / mirror / Atom feed
From: Farkas Levente <lfarkas@bnap.hu>
To: Hendrik Visage <hvisage@envisage.co.za>
Cc: linux-raid@vger.kernel.org
Subject: Re: how to which to bigger disk (md can do it?)
Date: Sun, 16 Nov 2003 17:36:58 +0100	[thread overview]
Message-ID: <3FB7A7AA.7010102@bnap.hu> (raw)
In-Reply-To: <20031116133137.GF25876@hvs.envisage.co.za>

Hendrik Visage wrote:
> On Sun, Nov 16, 2003 at 12:03:46PM +0100, Farkas Levente wrote:
> 
>>hi,
>>we've got a server with 3ware 7500-8 and 8 pieces of 120 GB maxtor hd 
>>and software raid-5. the 1TB disk is running out of the space so we 
> 
> 
> Are you sure about the Software RAID on this 3ware adapater?? I was
> under the impression it's a HW Raid adapter?
> (I have a preference to HW RAID if available...)

we've got a kernel creash with hardware raid 5 what's more software raid 
5 seems to be faster.

>>- put the 8 disk to another server and run rsync through two gigabit 
>>ethernet card. but it can takes more than a day to sync about 800GB.
> 
> 
> You could do this initially during the week before the swapout, and then
> just update it  before the swap out. Something te note, if it's lots of files,
> I'd advise to run multiple rsyncs over smaller directories, as it speeds
> up the rsync processing alot.

can't help since this is the backup server and almost everything 
changing on it.

>>- switch the disks one-by-one in the current server and leave linux's 
>>software raid to sync the data. in this case we only have to stop the 
>>system a few mintues per day and takes 8 days, but continous operation. 
>>does it possible? after I put all new hard disk the totel capacity will 
>>be (8-1)*200 GB or it will remain (8-1)*120 GB? since during the disk 
>>switch the total space is the smallest hd's*(n-1), but what happens when 
>>I put the last 200GB disk?
> 
> 
> If it's SW raid, it'll be based on the partitions, so you'll have to create the
> partitions bigger than the current 120GB partitions. Then after the last disk,
> the size would be the bigger size, however you'll then need to run a growfs
> (or similar) for your filesystem to expand it to the bigger size.

which partitions? it's not clear to me. we've got :
- 8 pieces of 120 GB Linux raid autodetect (/dev/sda1, /dev/sdb1 etc)
- 1 pieces of 840 GB ext3 (/dev/md2)
so which partition should I have to create and grow?
but what I'd like to prefere the cloning. is there any way to 'rsync' 
between a 120 GB and 200 GB disk which is Linux raid autodetect (and not 
eg. ext2)?

another good question anybody use 200 GB maxtor hd with 3ware 7500-8 
controller?

thanks.

-- 
   Levente                               "Si vis pacem para bellum!"



  reply	other threads:[~2003-11-16 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-16 11:03 how to which to bigger disk (md can do it?) Farkas Levente
2003-11-16 13:31 ` Hendrik Visage
2003-11-16 16:36   ` Farkas Levente [this message]
2003-11-16 17:38   ` Maurice Hilarius
2003-11-17  9:29 ` Luca Berra
2003-11-17  9:51   ` Neil Brown
2003-11-17 14:05     ` Farkas Levente
2003-11-17 20:24       ` Luca Berra
2003-11-17 22:29       ` Neil Brown

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=3FB7A7AA.7010102@bnap.hu \
    --to=lfarkas@bnap.hu \
    --cc=hvisage@envisage.co.za \
    --cc=linux-raid@vger.kernel.org \
    /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.