From: Doug Ledford <dledford@redhat.com>
To: Pim Zandbergen <P.Zandbergen@macroscoop.nl>
Cc: linux-raid@vger.kernel.org
Subject: Re: freshly grown array shrinks after first reboot - major data loss
Date: Thu, 01 Sep 2011 14:17:22 -0400 [thread overview]
Message-ID: <4E5FCC32.6020402@redhat.com> (raw)
In-Reply-To: <4E5FC495.7070909@macroscoop.nl>
On 09/01/2011 01:44 PM, Pim Zandbergen wrote:
> On 09/01/2011 06:31 PM, Doug Ledford wrote:
>> Why is your raid metadata using this old version? mdadm-3.2.2-6.fc15
>> will not create this version of raid array by default. There is a
>> reason we have updated to a new superblock.
>
> As you may have seen, the array was created in 2006, and has gone through
> several similar grow procedures.
Even so, one of the original limitations of the 0.90 superblock was
maximum usable device size. I'm not entirely sure that growing a 0.90
superblock past 2TB wasn't the source of your problem and that the bug
that needs fixed is that mdadm should have refused to grow a 0.90
superblock based array beyond the 2TB limit. Neil would have to speak
to that.
>> Does this problem still occur if you use a newer superblock format
>> (one of the version 1.x versions)?
>
> I suppose not. But that would destroy the "evidence" of a possible bug.
> For me, it's too late, but finding it could help others to prevent this
> situation.
> If there's anything I could do to help find it, now is the time.
>
> If the people on this list know enough, I will proceed.
>
> Thanks,
> Pim
next prev parent reply other threads:[~2011-09-01 18:17 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 [this message]
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
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=4E5FCC32.6020402@redhat.com \
--to=dledford@redhat.com \
--cc=P.Zandbergen@macroscoop.nl \
--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).