public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: agk@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2/doc example.conf.in
Date: Mon, 14 May 2012 16:29:00 -0000 [thread overview]
Message-ID: <20120514162952.21162.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk@sourceware.org 2012-05-14 16:29:51
Modified files:
doc : example.conf.in
Log message:
Refer to details of snapshot of raid problem.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/doc/example.conf.in.diff?cvsroot=lvm2&r1=1.49&r2=1.50
--- LVM2/doc/example.conf.in 2012/05/10 00:18:49 1.49
+++ LVM2/doc/example.conf.in 2012/05/14 16:29:50 1.50
@@ -430,8 +430,12 @@
# "mirror" - The original RAID1 implementation provided by LVM2/DM. It is
# characterized by a flexible log solution (core, disk, mirrored)
# and by the necessity to block I/O while reconfiguring in the
- # event of a failure. Snapshots of this type of RAID1 can be
- # problematic.
+ # event of a failure.
+ #
+ # There is an inherent race in the dmeventd failure handling
+ # logic with snapshots of devices using this type of RAID1 that
+ # in the worst case could cause a deadlock.
+ # Ref: https://bugzilla.redhat.com/show_bug.cgi?id=817130#c10
#
# "raid1" - This implementation leverages MD's RAID1 personality through
# device-mapper. It is characterized by a lack of log options.
next reply other threads:[~2012-05-14 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 16:29 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-23 12:59 zkabelac
2012-05-10 0:18 agk
2012-04-27 18:37 jbrassow
2012-03-14 17:13 zkabelac
2011-04-26 9:09 prajnoha
2011-04-12 20:44 snitzer
2010-10-13 15:45 mornfall
2010-08-25 13:06 snitzer
2010-06-28 20:40 wysochanski
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=20120514162952.21162.qmail@sourceware.org \
--to=agk@sourceware.org \
--cc=lvm-devel@redhat.com \
--cc=lvm2-cvs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).