From: John Robinson <john.robinson@anonymous.org.uk>
To: Pim Zandbergen <P.Zandbergen@macroscoop.nl>
Cc: Doug Ledford <dledford@redhat.com>, linux-raid@vger.kernel.org
Subject: Re: freshly grown array shrinks after first reboot - major data loss
Date: Fri, 02 Sep 2011 12:06:06 +0100 [thread overview]
Message-ID: <4E60B89E.5020806@anonymous.org.uk> (raw)
In-Reply-To: <4E609FAC.6020303@macroscoop.nl>
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).
Cheers,
John.
next prev parent reply other threads:[~2011-09-02 11:06 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 [this message]
2011-09-09 19:30 ` Bill Davidsen
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=4E60B89E.5020806@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=P.Zandbergen@macroscoop.nl \
--cc=dledford@redhat.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 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).