From: Christoph Hellwig <hch@infradead.org>
To: NeilBrown <neilb@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>, linux-raid@vger.kernel.org
Subject: Re: examining the layout of an existing raid device?
Date: Mon, 26 Sep 2011 06:45:59 -0400 [thread overview]
Message-ID: <20110926104559.GA20448@infradead.org> (raw)
In-Reply-To: <20110926203248.7ff8303f@notabene.brown>
On Mon, Sep 26, 2011 at 08:32:48PM +1000, NeilBrown wrote:
> On Mon, 26 Sep 2011 06:18:24 -0400 Christoph Hellwig <hch@infradead.org>
> wrote:
>
> > Maybe I'm just stupid, but is there a way to figure out the exact
> > geometry (e.g. pretty print of the superblock) for an existing array
> > somehow? I couldn't find anything in the mdadm man page for it.
>
> mdadm -E /dev/sda
>
> will print the metadata on device /dev/sda which describes the array that it
> is a member of.
Ok, that includes the information I was looking for, including the
chunk size, and layout.
prev parent reply other threads:[~2011-09-26 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 10:18 examining the layout of an existing raid device? Christoph Hellwig
2011-09-26 10:32 ` NeilBrown
2011-09-26 10:45 ` Christoph Hellwig [this message]
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=20110926104559.GA20448@infradead.org \
--to=hch@infradead.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).