From: Bill Davidsen <davidsen@tmr.com>
To: John Robinson <john.robinson@anonymous.org.uk>
Cc: Pim Zandbergen <P.Zandbergen@macroscoop.nl>,
Doug Ledford <dledford@redhat.com>,
linux-raid@vger.kernel.org, Neil Brown <neilb@suse.de>
Subject: Re: freshly grown array shrinks after first reboot - major data loss
Date: Fri, 09 Sep 2011 15:30:52 -0400 [thread overview]
Message-ID: <4E6A696C.20901@tmr.com> (raw)
In-Reply-To: <4E60B89E.5020806@anonymous.org.uk>
John Robinson wrote:
> On 02/09/2011 10:19, Pim Zandbergen wrote:
>> On 09/01/2011 09:41 PM, Doug Ledford wrote:
>>>> I could file a bug on bugzilla.redhat.com if that would help.
>>>
>>> Feel free, it helps me track things.
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=735306
>
> I'm not sure whether it's just the --grow that should complain, or
> perhaps the earlier step of
> mdadm /dev/md/array-using-0.90-metadata --add /dev/3TB
> should also complain (even if it'll work with less than 2TiB in use,
> it ought to tell the user they won't be able to grow the array).
>
Perhaps Neil can confirm, but the limitation seems to be using 2TB as an
array member size, I am reasonably sure that if you had partitioned the
drives into two 1.5TB partitions you could have created the array just fine.
Note that this is just a speculation, not a suggestion to allow using
0.90 metadata, and I do realize that this array was created in the dark
ages, not being created new.
--
Bill Davidsen<davidsen@tmr.com>
We are not out of the woods yet, but we know the direction and have
taken the first step. The steps are many, but finite in number, and if
we persevere we will reach our destination. -me, 2010
next prev parent reply other threads:[~2011-09-09 19:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 15:28 freshly grown array shrinks after first reboot - major data loss Pim Zandbergen
2011-09-01 16:12 ` Pim Zandbergen
2011-09-01 16:16 ` Pim Zandbergen
2011-09-01 16:48 ` John Robinson
2011-09-01 17:21 ` Pim Zandbergen
2011-09-02 9:02 ` Pim Zandbergen
2011-09-02 10:33 ` Mikael Abrahamsson
2011-09-05 10:47 ` Pim Zandbergen
2011-09-01 16:31 ` Doug Ledford
2011-09-01 17:44 ` Pim Zandbergen
2011-09-01 18:17 ` Doug Ledford
2011-09-01 18:52 ` Pim Zandbergen
2011-09-01 19:41 ` Doug Ledford
2011-09-02 9:19 ` Pim Zandbergen
2011-09-02 11:06 ` John Robinson
2011-09-09 19:30 ` Bill Davidsen [this message]
2011-09-08 1:10 ` NeilBrown
2011-09-08 13:44 ` Pim Zandbergen
2011-09-02 5:32 ` Simon Matthews
2011-09-02 8:53 ` Pim Zandbergen
2011-09-01 17:03 ` Robin Hill
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=4E6A696C.20901@tmr.com \
--to=davidsen@tmr.com \
--cc=P.Zandbergen@macroscoop.nl \
--cc=dledford@redhat.com \
--cc=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.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.