From: thornber@redhat.com
To: christophe.varoqui@free.fr
Cc: thornber@redhat.com,
device-mapper development <dm-devel@redhat.com>,
linux-raid@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [dm-devel] [ANNOUNCE] multipath-tools-0.1.6
Date: Tue, 27 Apr 2004 10:09:31 +0000 [thread overview]
Message-ID: <20040427100930.GA24944@nimzo> (raw)
In-Reply-To: <1083059878.408e2ea6eab69@imp1-q.free.fr>
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
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg\x12297
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
WARNING: multiple messages have this Message-ID (diff)
From: thornber@redhat.com
To: christophe.varoqui@free.fr
Cc: thornber@redhat.com,
device-mapper development <dm-devel@redhat.com>,
linux-raid@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [dm-devel] [ANNOUNCE] multipath-tools-0.1.6
Date: Tue, 27 Apr 2004 11:09:31 +0100 [thread overview]
Message-ID: <20040427100930.GA24944@nimzo> (raw)
In-Reply-To: <1083059878.408e2ea6eab69@imp1-q.free.fr>
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
next prev parent reply other threads:[~2004-04-27 10:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-25 21:54 [ANNOUNCE] multipath-tools-0.1.6 christophe varoqui
2004-04-25 21:54 ` christophe varoqui
2004-04-26 8:18 ` [dm-devel] " thornber
2004-04-26 8:18 ` thornber
2004-04-27 9:57 ` christophe.varoqui
2004-04-27 9:57 ` christophe.varoqui
2004-04-27 10:09 ` thornber [this message]
2004-04-27 10:09 ` thornber
2004-04-27 12:37 ` christophe.varoqui
2004-04-27 12:37 ` christophe.varoqui
2004-04-27 15:32 ` Mike Tran
2004-04-27 15:40 ` Mike Tran
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=20040427100930.GA24944@nimzo \
--to=thornber@redhat.com \
--cc=christophe.varoqui@free.fr \
--cc=dm-devel@redhat.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--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.