All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Hubert Reevez <hubereevez@gmail.com>,
	Jeff Johnson <jeff.johnson@aeoncomputing.com>,
	linux-raid@vger.kernel.org
Subject: Re: can't add a larger spare for a failed smaller disk
Date: Sun, 25 Jun 2017 19:55:16 +0100	[thread overview]
Message-ID: <59500714.5050407@youngman.org.uk> (raw)
In-Reply-To: <CAAK+==Y_P8hdhRoHnbGK7NujMYe2ERs6wztA-7CP_4MpZxZTRw@mail.gmail.com>

On 25/06/17 19:32, Hubert Reevez wrote:
> All seems to went good, but data offset are not equal on sdc and sdg,
> should I grow ? or something else ? thanks again
> 
That's normal on an array to which "things have happened".

If you grow or shrink or do other things which need to move data around,
the operation moves the data to a new offset to avoid having to have a
backup file.

And it does this on a per-disk basis, so if you if you change the raid
type, or you add a disk, or you do whole bunch of assorted operations,
the data could end up shuffled back and forth all over the place.

Bottom line - it's expected behaviour, don't worry.

Have you read the raid wiki? I get the impression you're not that au
fait with how raid works - a little bit of study might not go amiss :-)
> 
> md0 : active raid6 sdf[0] sdg[6] sdb[4] sde[3] sda[2] sdc[7]
> 5860548608 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU]
> 
> 
> mdadm -E : https://pastebin.com/hs7F5Ppi

Cheers,
Wol


  reply	other threads:[~2017-06-25 18:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-24 22:21 can't add a larger spare for a failed smaller disk Hubert Reevez
2017-06-24 23:23 ` Reindl Harald
     [not found] ` <CAFCYAsePbzqj7=0BORYGSvQFAOY9SCDAfX1hQmj-8gH2dFj3WA@mail.gmail.com>
2017-06-25  8:15   ` Hubert Reevez
     [not found]   ` <CAAK+==YbNyjFryhDmJe2Y67rcGzZKvaKX2BaEJzZTuMTN98jRw@mail.gmail.com>
     [not found]     ` <CAFCYAsexbWzffTdouwjQQf0=ZrSx+67c3rWtHcTX9K0nZ5Uuxw@mail.gmail.com>
     [not found]       ` <CAAK+==Y1h9GPw-5jmtnXKNPP6aYz3ezKre-MKSPvW9Sbjv7hdQ@mail.gmail.com>
     [not found]         ` <CAFCYAsdDdBVxFuj1S_5vOTNO3KN0mqA+hjbD99Ea53AadXuMFA@mail.gmail.com>
2017-06-25 10:10           ` Hubert Reevez
2017-06-25 10:35             ` Hubert Reevez
2017-06-25 18:32               ` Hubert Reevez
2017-06-25 18:55                 ` Wols Lists [this message]
2017-06-25 23:30                 ` Peter Grandi

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=59500714.5050407@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=hubereevez@gmail.com \
    --cc=jeff.johnson@aeoncomputing.com \
    --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.