All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Dominique <dcouot@hotmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid 5 to 6 migration
Date: Tue, 05 Feb 2013 08:04:12 -0500	[thread overview]
Message-ID: <5111034C.4000009@turmel.org> (raw)
In-Reply-To: <BLU0-SMTP1112AC3113196A419EBCD79C9000@phx.gbl>

On 02/05/2013 05:36 AM, Dominique wrote:
> 
> Thanks for the detailled answer. I read through all of it to identify
> what I did not understood before starting. I have a few clarificacions
> for you and a few questions.
> 
> Yes, that's the way my console looks like. I usually don't have problem
> with UTF8 output (i.e. not garbled), I figured it was the result of the
> lsdrv.... Nasty to read, but it's all there.

Thanks for the report.  I'll have to set up a VM with your distro and
play a bit.

> I am running Ubuntu 12.04.1 server on this relatively new raid5 setup.
> I think I understood most of the reshaping instructions, but I need to
> clarify your point related to the timeout. I tried to execute it in a
> simple bash file and got stopped at the beginning just for the lack of a
> timeoutfile?
> 
> After looking for it, I realised that sd[abcdef] were all symlinks
> pointing to another part of the system, where there is no driver
> directory. After browsing, i figured out that /sys/block/sda/device did
> led to a timeout file. Can you please confirm, it is the one we want ?

Yes, sorry.  Typo on my part.

> A last point I need to clarify: is the reshaping (although long) data
> destructive (backup will be done in all cases)?

The reshape may need a small backup file for critical section(s).  If it
does, it will refuse to proceed until you specify one with
"--backup-file=..." in the "--grow" operation.  If your system crashes
during the reshape, be sure to specify the same backup file when
re-assembling.

But yes, redundancy is maintained throughout the reshape.

> Thanks,

You're welcome.

Phil


      reply	other threads:[~2013-02-05 13:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 17:17 Raid 5 to 6 migration Dominique
2013-02-01 17:50 ` Phil Turmel
2013-02-01 18:16   ` Roman Mamedov
2013-02-01 18:19     ` Phil Turmel
2013-02-01 18:49       ` Chris Murphy
2013-02-01 22:04         ` Phil Turmel
2013-02-01 22:38           ` Chris Murphy
     [not found]   ` <COL114-W137DD8871889508BBF087BC91C0@phx.gbl>
2013-02-01 18:22     ` Phil Turmel
2013-02-03 10:00       ` Roy Sigurd Karlsbakk
2013-02-03 14:30         ` Phil Turmel
2013-02-03 22:01           ` Robin Hill
2013-02-04 12:51       ` Dominique
2013-02-04 18:39         ` Phil Turmel
2013-02-05  0:58           ` Brad Campbell
2013-02-05 10:36           ` Dominique
2013-02-05 13:04             ` Phil Turmel [this message]

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=5111034C.4000009@turmel.org \
    --to=philip@turmel.org \
    --cc=dcouot@hotmail.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.