From: Andre Noll <maan@systemlinux.org>
To: NeilBrown <neilb@suse.de>
Cc: Doug Ledford <dledford@redhat.com>,
Matthias Urlichs <matthias@urlichs.de>,
linux-raid@vger.kernel.org
Subject: Re: RAID1 assembled broken array
Date: Thu, 17 Sep 2009 10:25:28 +0200 [thread overview]
Message-ID: <20090917082528.GO5174@skl-net.de> (raw)
In-Reply-To: <65549e07fd6559855af68b60783213c3.squirrel@neil.brown.name>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
On 07:01, NeilBrown wrote:
> > Wrong lesson. The correct lesson to gather from this is to prefer
> > version 1.1 or 1.2 superblocks wherever possible. Superblocks at the
> > beginning of the device disappear when there is no partition table,
> > superblocks at the end can be confused for superblocks belonging to
> > the whole device when there is no partition table.
>
> 1.0 also protects from this problem. The 1.x metadata stores the
> offset of the superblock from the start of the device. That will appear
> to be wrong if you find a partition-superblock when reading from a
> whole-device, so mdadm will reject the device as not having a valid
> superblock.
BTW: Why are new arrays still created with 0.90 metadata format by
default?
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-09-17 8:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 19:22 RAID1 assembled broken array Matthias Urlichs
2009-09-15 19:24 ` Majed B.
2009-09-15 19:33 ` Matthias Urlichs
2009-09-15 19:43 ` Majed B.
2009-09-15 20:04 ` Doug Ledford
2009-09-15 20:00 ` Doug Ledford
2009-09-15 20:27 ` Matthias Urlichs
2009-09-15 21:01 ` NeilBrown
2009-09-16 4:50 ` Matthias Urlichs
2009-09-17 16:44 ` Doug Ledford
2009-09-17 17:09 ` Matthias Urlichs
2009-09-17 17:12 ` Majed B.
2009-09-25 8:07 ` Neil Brown
2009-09-17 8:25 ` Andre Noll [this message]
2009-09-25 8:12 ` Neil Brown
2009-09-25 10:42 ` Chris Webb
2009-09-26 9:58 ` Andre Noll
2009-09-26 13:01 ` John Robinson
2009-09-26 19:21 ` Clinton Lee Taylor
2009-09-28 16:12 ` Andre Noll
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=20090917082528.GO5174@skl-net.de \
--to=maan@systemlinux.org \
--cc=dledford@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=matthias@urlichs.de \
--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 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).