linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Another Sillyname <anothersname@googlemail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: linux-raid@vger.kernel.org
Subject: Re: Fwd: Installing Linux directly onto RAID6 Array...........
Date: Sun, 24 May 2015 11:07:31 +0100	[thread overview]
Message-ID: <CAOS+5GF22YN8OagwQiXy4gxn94eTLt-X31VhWoU47r_kgLLYnQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1505241142350.9487@uplift.swm.pp.se>

But reading this.....

https://raid.wiki.kernel.org/index.php/RAID_superblock_formats#The_version-1_Superblock_Format

it makes a sound argument for the metadata superblock being at the
beginning of the drive.......in a nutshell the kernel can 'construct'
the md device easier if the metadata is at the beginning....as well as
data resilience issues in the case of a crash.



On 24 May 2015 at 10:46, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> On Sun, 24 May 2015, Another Sillyname wrote:
>
>> I suspect you're correct in that I'll end up with the boot partitions
>> being in RAID1 and the data in RAID6, however I am seriously
>> considering having the boot in RAID6 as well...if I can integrate the
>> mdadm.conf into the initramfs properly I can't see a reason not to do
>> this?
>
>
> The initramfs is usually located on the boot partition. A raid1 partition
> with a filesystem can be read by the bootloader even if the bootloader
> doesn't understand to start the raid first. This is not possible with raid6.
>
> So /boot is usually raid1.
>
>> Had a look at the metadata=0.9 option but reading the info on mdadm
>> metadata I think I'd prefer to have the metadata at the start of the
>> drive, also it looks like metadata=1.2 has extra functionality that I
>> may want to use later.
>
>
> Look at v1.0 superblock, it has the same functionality but stores the
> superblock at the end.
>
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se

  reply	other threads:[~2015-05-24 10:07 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 10:08 Installing Linux directly onto RAID6 Array Another Sillyname
2015-05-12 10:20 ` Rudy Zijlstra
2015-05-12 12:20   ` Phil Turmel
2015-05-12 12:31     ` Roman Mamedov
     [not found]       ` <CAOS+5GHhUoYxTTYOWU7cdN6GSdffSMGrhWHU5ZtWEjc4jEm3eg@mail.gmail.com>
2015-05-12 13:12         ` Fwd: " Another Sillyname
2015-05-12 13:42           ` Roman Mamedov
2015-05-12 13:27 ` Wilson, Jonathan
2015-05-12 14:05   ` Another Sillyname
2015-05-13  0:02 ` Adam Goryachev
     [not found]   ` <CAOS+5GEP6+7OAHkqQjeyGHAB5u-_-Vq2JWGpcOemYHdCjmR5Lg@mail.gmail.com>
2015-05-24  1:18     ` Fwd: " Another Sillyname
2015-05-24  8:36       ` Mikael Abrahamsson
2015-05-24  9:08         ` Another Sillyname
2015-05-24  9:46           ` Mikael Abrahamsson
2015-05-24 10:07             ` Another Sillyname [this message]
2015-05-24 10:35               ` Mikael Abrahamsson
2015-05-24 10:42                 ` Another Sillyname
2015-05-26  8:29           ` NeilBrown
2015-05-26 13:18             ` Another Sillyname
2015-05-24 11:12         ` Fwd: " Wols Lists
2015-05-24 11:57           ` Brad Campbell
2015-05-24 12:41             ` Wols Lists
2015-05-24 13:48               ` Brad Campbell
2015-05-24 14:06               ` Mikael Abrahamsson
2015-05-24 14:53                 ` Wols Lists
2015-05-24 14:57                   ` Mikael Abrahamsson
2015-05-25 21:03                     ` Another Sillyname
2015-05-25 23:20                       ` Wols Lists
2015-05-26  7:08                         ` Another Sillyname
2015-05-26  8:06                           ` Mikael Abrahamsson
2015-05-26 11:18                             ` Another Sillyname
2015-05-26 14:08                               ` Mikael Abrahamsson
2015-05-26 20:11                                 ` Wols Lists
2015-05-26 21:02                                   ` Another Sillyname
2015-05-27  4:59                                   ` Mikael Abrahamsson

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=CAOS+5GF22YN8OagwQiXy4gxn94eTLt-X31VhWoU47r_kgLLYnQ@mail.gmail.com \
    --to=anothersname@googlemail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=swmike@swm.pp.se \
    /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).