From: Robin Hill <robin@robinhill.me.uk>
To: Matt Callaghan <matt_callaghan@sympatico.ca>
Cc: linux-raid@vger.kernel.org
Subject: Re: Growing Array (More Devices) - new devices are slightly smaller than the existing drives, unable to shrink array
Date: Sat, 28 Sep 2013 16:28:57 +0100 [thread overview]
Message-ID: <20130928152857.GA10073@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <BLU0-SMTP69424F8624CF692DCD2AD7812A0@phx.gbl>
[-- Attachment #1: Type: text/plain, Size: 2338 bytes --]
On Sat Sep 28, 2013 at 10:49:49AM -0400, Matt Callaghan wrote:
> Hello mdadm Linux-RAID experts;
>
> My Goal: Expand (grow) my array from 6xHDD (RAID6) to 8xHDD (RAID6)
>
> This is my root cause problem: when I went to try to add the new drive
> (already formatted for Linux RAID partition):
>
> fermulator@fermmy-server:~$ sudo mdadm --add /dev/md2000 /dev/sdq1
> mdadm: /dev/sdq1 not large enough to join array
>
> As I have researched and learned, I need to:
> A) shrink the filesystem (ext4) -- done (shrunk by a generous 1.6GB)
> B) shrink the array size -- incomplete (unable to proceed, the --grow
> command doesn't do anything)
>
> I've been following this guide:
> http://webapp5.rrz.uni-hamburg.de/SuSe-Dokumentation/manual/sles-manuals_en/manual/raidresize.html#resizedecrraid
>
>
> This pastebin shows my array details, the 'existing' drives (fdisk) and
> 'new' drives (fdisk) - http://pastebin.com/U04VJpE4
>
> Any ideas?
>
Firstly, your new drives are exactly the same size as the old ones:
Disk /dev/sdk: 2000.4 GB, 2000398934016 bytes
Disk /dev/sdq: 2000.4 GB, 2000398934016 bytes
Your partition sizes are different though, probably because newer
versions on fdisk default to a higher start point. You can replicate the
partitions from the old disks onto the new ones using sfdisk:
sfdisk -d /dev/sdk | sfdisk /dev/sdq
You can do the same thing manually using fdisk - just make sure you set
the units to sectors (fdisk -u=sectors) as the cylinder information
differs between the disks (and is obsolete and meaningless).
If you do want to stick with the partitions you have and continue with
shrinking the array, the value passed with the "-z" parameter is the
device size, not the array size. You're passing a value larger than the
disk size, so it's being ignored. It also needs to be a multiple of the
chunk size (64k in your case). So you need to take your 7812441960,
divide by the number of active disks (4) and round up to the nearest
64k. This gives you a new device size of 1953110528.
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-09-28 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-28 14:49 Growing Array (More Devices) - new devices are slightly smaller than the existing drives, unable to shrink array Matt Callaghan
2013-09-28 15:28 ` Robin Hill [this message]
2013-09-29 2:14 ` Matt Callaghan
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=20130928152857.GA10073@cthulhu.home.robinhill.me.uk \
--to=robin@robinhill.me.uk \
--cc=linux-raid@vger.kernel.org \
--cc=matt_callaghan@sympatico.ca \
/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).