From: Tomasz Chmielewski <tch@wpkg.org>
To: stefan.huebner@stud.tu-ilmenau.de,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: not able to resize/grow RAID-1 (beyond 1 TB?)
Date: Sat, 14 Jan 2012 22:15:59 +0100 [thread overview]
Message-ID: <4F11F08F.4070706@wpkg.org> (raw)
In-Reply-To: <4F11E4F4.1030309@stud.tu-ilmenau.de>
On 01/14/2012 09:26 PM, Stefan /*St0fF*/ Hübner wrote:
> Hi Tomasz,
>
> at first: if you had 1TB drives before, dd'ed them to the new 3TB drives
> and changed the partitioning scheme accordingly - that all looks OK.
> The weird thing here is that 1TB disks never had 1024GiB, but 931GiB.
> So the reshape has already happened to "the system's maximum".
>
> I do suspect you have a 32bit system and mdadm is not the latest version?
No, the system was 64 bit from the very beginning; mdadm may not be the
latest one, but is far from being obsoletes, too (Debian Squeeze).
The issue is actually solved now.
What I had to do was:
mdadm /dev/md2 -f /dev/sdb3
mdadm /dev/md2 -r /dev/sdb3
# not necessarily 10 MB needs cleaning, but it's a small number...
dd if=/dev/zero of=/dev/sdb3 bs=1M count=10
mdadm /dev/md2 -a /dev/sdb3
# wait till it syncs, and do the same for /dev/sda3
reboot
If I did the same without dd if=/dev/zero, it somehow didn't want to
work and /dev/md2 was still only 1 TB big.
Unless I've messed up somewhere!
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-01-14 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 20:35 not able to resize/grow RAID-1 (beyond 1 TB?) Tomasz Chmielewski
[not found] ` <4F11E4F4.1030309@stud.tu-ilmenau.de>
2012-01-14 21:15 ` Tomasz Chmielewski [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=4F11F08F.4070706@wpkg.org \
--to=tch@wpkg.org \
--cc=linux-raid@vger.kernel.org \
--cc=stefan.huebner@stud.tu-ilmenau.de \
/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.