Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Mike Tran <mhtran@us.ibm.com>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [dm-devel] [ANNOUNCE] multipath-tools-0.1.6
Date: 27 Apr 2004 10:40:21 -0500	[thread overview]
Message-ID: <1083080421.21372.21.camel@star2.austin.ibm.com> (raw)
In-Reply-To: <1083079947.21372.16.camel@star2.austin.ibm.com>

On Tue, 2004-04-27 at 10:32, Mike Tran wrote:
> On Tue, 2004-04-27 at 05:09, thornber@redhat.com wrote:
> > On Tue, Apr 27, 2004 at 11:57:58AM +0200, christophe.varoqui@free.fr wrote:
> > > Selon thornber@redhat.com:
> > > 
> > > > On Sun, Apr 25, 2004 at 11:54:59PM +0200, christophe varoqui wrote:
> > > > > * add the dmadm WIP tool (read MD superblocks and create
> > > > >   corresponding devmaps when possible)
> > > > 
> > > > :)
> > > > 
> > > Any insight on where to put the log of the mirror target when mapping over a
> > > MD-created raid1 ?
> > 
> > MD effectively uses a log with a single region in it.  So we only need
> > 3 sectors (2 for the header 1 for the bitset) for the log, is there
> > any space in the MD metadata where this could be placed ?
> > 
> > - Joe
> 
> The MD device size is 64K aligned and MD superblock size is 4K.  In term
> of sectors, the calculation is as follows:

Oops.  I was thinking raid1 when saying : "The MD device size is 64K
aligned."  I should have said : "The new MD child size is 64K aligned."

Mike T.


      reply	other threads:[~2004-04-27 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-25 21:54 [ANNOUNCE] multipath-tools-0.1.6 christophe varoqui
2004-04-26  8:18 ` [dm-devel] " thornber
2004-04-27  9:57   ` christophe.varoqui
2004-04-27 10:09     ` thornber
2004-04-27 12:37       ` christophe.varoqui
2004-04-27 15:32       ` Mike Tran
2004-04-27 15:40         ` Mike Tran [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=1083080421.21372.21.camel@star2.austin.ibm.com \
    --to=mhtran@us.ibm.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