From: Takahiro Yasui <tyasui@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH 0 of 13] LVM add 'mirrored' log type
Date: Mon, 22 Feb 2010 04:09:29 -0500 [thread overview]
Message-ID: <4B8249C9.9060602@redhat.com> (raw)
In-Reply-To: <1266429310.29358.35.camel@hydrogen.msp.redhat.com>
Jonathan Brassow wrote:
> I've fixed the segfaults Taka reported. I've also begun to go through
> and fix the remaining issues with handling device failures in the
> various different scenarios. I could use some help testing all the
> different variations. I've described below some of the different
> permutations that will now exist. I will be going through and testing
> these as well.
'lvconvert --repair' doen't work and canuses *deadlock*. when a VG contains
two PVs and one of PVs failed; This is a situation that a mirror leg and
one of mirrored logs broke at the same time.
When one of mirrored logs broke, I/Os to mirrored log are blocked and
kmirrord can't make forward until the log is fixed. However, lvocnvert
command tries to fix mirror legs before a mirrored log if a mirror leg
also broke.
During the procedure to fix a mirror leg, lv_suspend() is called in
_remove_mirror_images() and lv_suspend() which calls kernel function,
dm_suspend(), doesn't finish. Rough call trace is as follows:
dm_suspend()
mirror_presuspend()
flush_workqueue()
-> waiting kmirrored
-> waiting I/O to its log
I think that an error recovery of a log device should be done before
mirror legs are recovered.
Thanks,
Taka
next prev parent reply other threads:[~2010-02-22 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 17:55 [PATCH 0 of 13] LVM add 'mirrored' log type Jonathan Brassow
2010-02-18 16:48 ` Jonathan Brassow
2010-02-22 9:18 ` Takahiro Yasui
2010-02-22 9:09 ` Takahiro Yasui [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-17 17:53 Jonathan Brassow
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=4B8249C9.9060602@redhat.com \
--to=tyasui@redhat.com \
--cc=lvm-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.