linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tyler J. Wagner" <tyler@tolaris.com>
To: linux-raid@vger.kernel.org
Subject: alignment of metadata 1.2 and mkfs.ext4
Date: Wed, 06 Jul 2011 08:11:16 +0100	[thread overview]
Message-ID: <1309936276.11661.8.camel@baal> (raw)

Hi all (well, Neil, really),

The the following, Neil states that that is no issue with alignment of
metadata 1.2 and mkfs.ext4 on 4K drives:

http://www.issociate.de/board/post/507176/filesystem_on_mdadm_raid_from_unpartioned_block_devices.html

Sorry to ask again, but I just want to clarify. Metadata 1.2 puts the
data 4K from the start of the device/partition. Does mkfs put the start
of the filesystem at 64K from the start? IE, will the following align,
without any need for options?

(create partitions starting 2048 512-byte sectors from start = 1MB)
mdadm --create /dev/md0 -v --raid-devices=4 --level=raid10
--metadata=1.2 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1
mkfs.ext4 /dev/md0

And, slightly off-topic, it's not necessary to define stride and stripe
any longer?
mkfs.ext4 -E stride=16,stripe-width=32 /dev/md0

Regards,
Tyler


-- 
"The belief in immortality has always seemed cowardly to me. When very
young I learned that all things die, and all that we wish of good must
be won on this earth or not at all."
   -- Anne Smedley


             reply	other threads:[~2011-07-06  7:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06  7:11 Tyler J. Wagner [this message]
2011-07-06  8:35 ` alignment of metadata 1.2 and mkfs.ext4 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
  -- 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=1309936276.11661.8.camel@baal \
    --to=tyler@tolaris.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).