From: Robin Hill <robin@robinhill.me.uk>
To: "Tyler J. Wagner" <tyler@tolaris.com>
Cc: Roman Mamedov <rm@romanrm.ru>, linux-raid@vger.kernel.org
Subject: Re: alignment of metadata 1.2 and mkfs.ext4
Date: Wed, 6 Jul 2011 11:03:32 +0100 [thread overview]
Message-ID: <20110706100332.GA9957@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <1309945954.2685.2.camel@baal>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
On Wed Jul 06, 2011 at 10:52:34AM +0100, Tyler J. Wagner wrote:
> On Wed, 2011-07-06 at 15:20 +0600, Roman Mamedov wrote:
> > On Wed, 06 Jul 2011 08:11:16 +0100
> > "Tyler J. Wagner" <tyler@tolaris.com> wrote:
> >
> > > Metadata 1.2 puts the data 4K from the start of the device/partition.
> >
> > This is not correct. See mdadm -E /dev/sdX.
> >
> > $ sudo mdadm -E /dev/sdc3
> > /dev/sdc3:
> > ...
> > Version : 1.2
> > ...
> > Data Offset : 2048 sectors
> > ...
>
> That is very interesting. The mdadm man page, and everything I've seen
> online, all say "The different sub-versions store the superblock at
> different locations on the device, either at the end (for 1.0), at the
> start (for 1.1) or 4K from the start (for 1.2)."
>
That's the RAID superblock at 4K, not the data.
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-07-06 10:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 7:11 alignment of metadata 1.2 and mkfs.ext4 Tyler J. Wagner
2011-07-06 8:35 ` Werner Fischer
2011-07-06 9:20 ` Roman Mamedov
2011-07-06 9:52 ` Tyler J. Wagner
2011-07-06 10:02 ` Roman Mamedov
2011-07-06 13:40 ` Tyler J. Wagner
2011-07-06 10:03 ` Robin Hill [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-06 7:10 Tyler J. Wagner
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=20110706100332.GA9957@cthulhu.home.robinhill.me.uk \
--to=robin@robinhill.me.uk \
--cc=linux-raid@vger.kernel.org \
--cc=rm@romanrm.ru \
--cc=tyler@tolaris.com \
/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).