From: Takahiro Yasui <tyasui@redhat.com>
To: dm-devel@redhat.com
Cc: agk@redhat.com
Subject: Re: [RFC][PATCH 0/4] dm-log: support multi-log devices
Date: Mon, 22 Dec 2008 19:23:26 -0500 [thread overview]
Message-ID: <49502F7E.9040300@redhat.com> (raw)
In-Reply-To: <20081220001305.GA8574@us.ibm.com>
Hi Malahal,
malahal@us.ibm.com wrote:
> Takahiro Yasui [tyasui@redhat.com] wrote:
>> In addition, the multi-log feature is efficient and very important
>> at system booting. It is highly possible that disks get broken.
>> I think that the current log feature can not save this situation
>> because there is only one log disk and there is only way to construct
>> a mirror by "core" log. Then, a whole disk replication will be triggered.
>>
>> Do you have a good idea to save it, too? If there is, it could be
>> an another solution of our concern.
>
> A while back IBM posted a patch to LVM that constructs a log device with
> a mirror and then creates the real mirror using such a mirrored log
> device. I think this may solve your problem. It was completely written
> in LVM and Stefan refreshed it to the latest LVM.
Thank you for the comment and information. It seems that your
approach seems to address my problem, too. Here I have a concern
about write performance because an additional mirror mapping might
introduce additional delay and overhead. In addition, error for
log devices is better to be handled by the simple way, and a basic
error handling would work.
I couldn't find any discussion after you posted the patch.
Could you tell me if IBM also have the same background as I have,
or do you have another issue to solve? I would also like to know
if my approach solves your problem.
> Anyone thinks this user level only solution is any better? We will be
> very happy to have any one of the solutions in upstream!
Yes, I appreciate many comments and I'm glad to have a solution
in upstream, too.
> Here is a link the posted patch
> (http://permalink.gmane.org/gmane.linux.kernel.device-mapper.devel/3988)
>
>
> --Malahal.
next prev parent reply other threads:[~2008-12-23 0:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 0:01 [RFC][PATCH 0/4] dm-log: support multi-log devices Takahiro Yasui
2008-11-26 18:56 ` Phillip Susi
2008-11-27 7:50 ` Takahiro Yasui
2008-11-28 20:06 ` Phillip Susi
2008-12-01 7:00 ` Takahiro Yasui
2008-12-01 11:09 ` Michał Mirosław
2008-12-02 6:05 ` Takahiro Yasui
2008-12-01 16:10 ` Phillip Susi
2008-12-02 4:52 ` Takahiro Yasui
2008-12-12 20:21 ` Jonathan Brassow
2008-12-15 14:56 ` Takahiro Yasui
2008-12-20 0:13 ` malahal
2008-12-23 0:23 ` Takahiro Yasui [this message]
2008-12-23 18:02 ` malahal
2008-12-31 20:15 ` malahal
2009-01-08 18:30 ` Jonathan Brassow
2009-01-08 19:00 ` malahal
2009-01-05 15:44 ` Takahiro Yasui
2009-01-05 16:24 ` malahal
2009-01-05 17:36 ` Takahiro Yasui
2009-01-05 18:44 ` malahal
2009-01-05 18:51 ` Alasdair G Kergon
2009-01-05 22:21 ` Takahiro Yasui
2009-01-05 22:26 ` Takahiro Yasui
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=49502F7E.9040300@redhat.com \
--to=tyasui@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
/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.