From: NeilBrown <neilb@suse.de>
To: Gionatan Danti <g.danti@assyoma.it>
Cc: linux-raid@vger.kernel.org, keld@keldix.com
Subject: Re: RAID 10 far and offset on-disk layouts
Date: Mon, 13 Jan 2014 10:20:21 +1100 [thread overview]
Message-ID: <20140113102021.1ef3e203@notabene.brown> (raw)
In-Reply-To: <52CE57D9.1030501@assyoma.it>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
On Thu, 09 Jan 2014 09:03:37 +0100 Gionatan Danti <g.danti@assyoma.it> wrote:
> >>
> >> Interesting. Two question:
> >> 1) from which kernel the layout is the one depicted by Wikipedia?
Exactly what depiction in wikipedia are you referring to? A link to the
image might help.
> >> 2) it is possible, using mdadm, check what "far" layout is in use?
mdadm --detail /dev/mdWHATEVER | grep Layout
> >
> > I cannot answer that. Neil Brown should know.
> >
> > Best regards
> > Keld
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
> Hi all,
> anyone with an update on these two questions?
>
> I was thinking to use the kernel block trace facility to track disk
> access and infer the on-disk data structure, but I haven't tried for now.
>
> On the other hand, I carefully looked at mdadm output, without finding
> anything related to physical block placing.
Look for "Layout".
NeilBrown
>
> Any new advices on that regard?
> Thanks.
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-01-12 23:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 14:29 RAID 10 far and offset on-disk layouts Gionatan Danti
2013-12-27 14:46 ` Peter Grandi
2013-12-27 15:16 ` Gionatan Danti
2013-12-27 17:16 ` Peter Grandi
2013-12-27 17:32 ` Gionatan Danti
2013-12-27 18:26 ` keld
2013-12-27 15:19 ` keld
2013-12-27 15:22 ` Gionatan Danti
2013-12-27 15:49 ` keld
2014-01-09 8:03 ` Gionatan Danti
2014-01-12 23:20 ` NeilBrown [this message]
2014-01-13 8:52 ` Gionatan Danti
2014-01-13 9:45 ` NeilBrown
2014-01-13 10:15 ` Gionatan Danti
2014-01-13 22:27 ` NeilBrown
2014-01-13 23:38 ` keld
2014-01-14 0:46 ` Stan Hoeppner
2014-01-14 9:38 ` keld
2014-01-14 9:06 ` Gionatan Danti
2014-01-14 9:16 ` NeilBrown
2014-01-14 9:27 ` Gionatan Danti
2014-01-14 10:06 ` keld
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=20140113102021.1ef3e203@notabene.brown \
--to=neilb@suse.de \
--cc=g.danti@assyoma.it \
--cc=keld@keldix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.