linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek <mlf.conv@gmail.com>
To: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Fwd: mdadm format for manual destriping
Date: Mon, 26 Oct 2015 19:09:47 +0100	[thread overview]
Message-ID: <CA+sqOsZzk3kTPK-rkvyDyhZCwBot_bOaVT8XbW5-h8c2YVn1Mw@mail.gmail.com> (raw)
In-Reply-To: <CA+sqOsY5UwwGbnHVQ+ctBGKo1FEOWWbAqWBmYCqo4Z6tVTL4Kw@mail.gmail.com>

I have found the following link which answers question 1.
But there's more stuff that's seems undocumented
https://raid.wiki.kernel.org/index.php/RAID_superblock_formats
Question 2
Does the superblock of size 256+2 start at 0?
Does the first block start immediately after 258 bytes?
Also question 3,4,5

Marek

On Saturday, October 24, 2015, Marek <mlf.conv@gmail.com> wrote:
>
> Hi,
>
> is there a documentation available on how mdadm stores data? E.g.
> 1.  super-block
> 2.  offset of first block on each drive
> 3. whether mdadm stores blocks as raw data or stores some kind of
> metadata associated with each block e.g. disk 1 -> data_block1
> immidiatelly followed by data_block 5 or
> metadata_for_block_1 | data_block 1 |  metadata_for_block_5 | data_block 5 |
> 4. how and where mdadm stores its backup superblock
> 5. what klind of XOR algorithm is used by mdadm
>
> thanks,
>
> Marek

  parent reply	other threads:[~2015-10-26 18:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-24 19:28 mdadm format for manual destriping Marek
     [not found] ` <CA+sqOsY5UwwGbnHVQ+ctBGKo1FEOWWbAqWBmYCqo4Z6tVTL4Kw@mail.gmail.com>
2015-10-26 18:09   ` Marek [this message]
2015-10-26 19:13     ` Fwd: " Phil Turmel

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=CA+sqOsZzk3kTPK-rkvyDyhZCwBot_bOaVT8XbW5-h8c2YVn1Mw@mail.gmail.com \
    --to=mlf.conv@gmail.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).