From: Chris Webb <chris@arachsys.com>
To: Peter Rabbitson <rabbit+list@rabbit.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: Trouble increasing md component size
Date: Wed, 18 Jun 2008 21:00:36 +0100 [thread overview]
Message-ID: <20080618200036.GB30682@arachsys.com> (raw)
In-Reply-To: <4859605D.90509@rabbit.us>
Peter Rabbitson <rabbit+list@rabbit.us> writes:
> I had exactly the same problem some months ago. The key is in the
> (obscure) assembly option --update=devicesize. Find it in the mdadm
> manpage and the whole picture will come together instantly. The wisdom is
> not very widespread as this affects only V1.1 and 1.2 superblocks.
Thanks, that's great. I've been using a man page slightly older (2.5.6) than
the mdadm binary I'm using (2.6.7), which doesn't mention update=devicesize,
although I'd probably have missed it anyway!
However, is there a way to do this without stopping the array first? I'm
using it as an LVM PV and slicing it up into logical volumes which clients
will be running off while I'm wanting to grow it.
Cheers,
Chris.
next prev parent reply other threads:[~2008-06-18 20:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 18:26 Trouble increasing md component size Chris Webb
2008-06-18 19:22 ` Peter Rabbitson
2008-06-18 20:00 ` Chris Webb [this message]
2008-06-19 3:42 ` Neil Brown
2008-06-19 15:45 ` Chris Webb
2008-06-19 23:10 ` Chris Webb
2008-06-19 23:49 ` Chris Webb
2008-06-20 11:13 ` Chris Webb
2008-06-20 14:24 ` Chris Webb
2008-06-23 1:26 ` Neil Brown
2008-06-23 11:18 ` Chris Webb
2008-06-23 22:53 ` Neil Brown
2008-06-24 11:47 ` Chris Webb
2008-06-24 23:19 ` Chris Webb
2008-09-17 18:11 ` [PATCH] md: Fix rdev_size_store with size = 0 Chris Webb
2008-10-07 12:40 ` [Resend] " Chris Webb
2008-10-13 0:54 ` Neil Brown
2008-06-24 2:40 ` Trouble increasing md component size 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=20080618200036.GB30682@arachsys.com \
--to=chris@arachsys.com \
--cc=linux-raid@vger.kernel.org \
--cc=rabbit+list@rabbit.us \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).