All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Ben Kamen <benjammin2068@gmail.com>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Using mdadm --grow to resize a RAID1
Date: Mon, 2 Jan 2017 18:52:05 +0000	[thread overview]
Message-ID: <586AA155.9000802@youngman.org.uk> (raw)
In-Reply-To: <CADDTLRA2fNyKTCsxK_G-2k4p-01wn16M7T_ruRxt_Dot+6-8Aw@mail.gmail.com>

On 02/01/17 18:38, Ben Kamen wrote:
> On Mon, Jan 2, 2017 at 12:17 PM, Wols Lists <antlists@youngman.org.uk> wrote:
>> On 02/01/17 17:59, Ben Kamen wrote:
>>> Sounds like I have to do this from single user mode or an boot disk/CD?
>>
>> Important snippet of information we should have asked and I don't
>> remember seeing ... what kernel and mdadm are you using?
> 
> 
> My bad...
> 
> kernel is 2.6.32-642.11.1.el6.centos.plus.x86_64
> mdadm.x86_64 is 3.3.4-1.el6_8.5
> 
OUCH!

I don't know how far the kernel and mdadm have come since then, and what
has or has not been backported, but it sounds like you want a modern
rescue CD.

I'd be inclined to get something like SystemRescueCD
https://www.system-rescue-cd.org/SystemRescueCd_Homepage and see if the
mdadm and kernel on that work any better. It wouldn't surprise me if
they do.

Cheers,
Wol


  reply	other threads:[~2017-01-02 18:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-02 10:18 Using mdadm --grow to resize a RAID1 Benjammin2068
2017-01-02 12:19 ` Wols Lists
2017-01-02 15:55   ` Benjammin2068
2017-01-02 16:14     ` Jack Wang
2017-01-02 16:19       ` Wols Lists
2017-01-02 16:24     ` Roman Mamedov
2017-01-02 16:38       ` Benjammin2068
2017-01-02 17:59         ` Ben Kamen
2017-01-02 18:17           ` Wols Lists
2017-01-02 18:38             ` Ben Kamen
2017-01-02 18:52               ` Wols Lists [this message]
2017-01-02 19:11                 ` Ben Kamen
2017-01-03  1:57                 ` Ben Kamen

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=586AA155.9000802@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=benjammin2068@gmail.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.