All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Rabbitson <rabbit@rabbit.us>
To: Nagy Zoltan <kirk@bteam.hu>
Cc: linux-raid@vger.kernel.org
Subject: Re: component growing in raid5
Date: Mon, 24 Mar 2008 08:09:35 +0100	[thread overview]
Message-ID: <47E753AF.5050507@rabbit.us> (raw)
In-Reply-To: <47E5FFB8.5030903@bteam.hu>

Nagy Zoltan wrote:
> hi all,
> 
> i've set up a two dimensional array:
>    * leaf nodes composes raid5 arrays from their disks, and export it as 
> a iSCSI target
>    * the root node creates a raid5 on top of the exported targets
> 
> in this setup i will have to face that an array component can(and would) 
> grow, so i
> created a test case for this to see what comes out ;)
>    * after growing the components mdadm won't recognized them anymore as 
> an array member
>        (because there are no superblock at the end of the device - last 
> 64k?)
>       i've tried to inform mdadm about the size of the components, but 
> it sad no ;)
>    * i've added an arbitary superblock copy operation after the 
> expansion, to make possible for
>   mdadm to recognize and assemble the array - it's working, and passes 
> my test.
> 
> is there a less 'funky' solution for this ;)
> can i run into any trouble when doing this on the real system?
> 

I would simply use a v1.1 superblock which will be situated at the start of 
the array. Then you will face another problem - once you grow a leaf device, 
mdadm will not see the new size as it will find the superblock at sect 0 and 
will be done there. You will need to issue mdadm -A ... --update devicesize. 
The rest of the operations are identical.

As a side note I am also curious why do you go the raid55 path (I am not very 
impressed however :)

Peter

  parent reply	other threads:[~2008-03-24  7:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-23  6:59 component growing in raid5 Nagy Zoltan
2008-03-23 11:24 ` Peter Grandi
2008-03-24  7:09 ` Peter Rabbitson [this message]
2008-03-24  7:09 ` Peter Rabbitson
2008-03-24 15:17   ` Nagy Zoltan
2008-03-24 15:42     ` Peter Rabbitson
2008-03-24 16:52       ` Nagy Zoltan
2008-03-25 13:06     ` Peter Grandi
2008-03-25 13:38       ` Mattias Wadenstein
2008-03-25 20:02         ` Peter Grandi
2008-03-27 20:44           ` Mattias Wadenstein
2008-03-27 22:09             ` Richard Scobie
2008-03-28  8:07               ` Mattias Wadenstein

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=47E753AF.5050507@rabbit.us \
    --to=rabbit@rabbit.us \
    --cc=kirk@bteam.hu \
    --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.