public inbox for cluster-cvs@sourceware.org help / color / mirror / Atom feed
From: jbrassow@sourceware.org To: cluster-cvs@sources.redhat.com Subject: cluster/cmirror-kernel/src dm-cmirror-client.c ... Date: Wed, 26 Sep 2007 03:15:00 -0000 [thread overview] Message-ID: <20070926031541.29694.qmail@sourceware.org> (raw) CVSROOT: /cvs/cluster Module name: cluster Branch: RHEL4 Changes by: jbrassow@sourceware.org 2007-09-26 03:15:41 Modified files: cmirror-kernel/src: dm-cmirror-client.c dm-cmirror-common.h dm-cmirror-server.c Log message: Bug 291521: Cluster mirror can become out-of-sync if nominal I/O overl... Another touch-up for this bug. Bad news: Because a node can cache the state of a region indefinitely (especially for blocks that are used alot - e.g. a journaling area of a file system), we must deny writes to any region of the mirror that is not yet recovered. This is only the case with cluster mirroring. This means poor performance of nominal I/O during recovery - probably really bad performance. However, this is absolutely necessary for mirror reliability. Good news: The time I spent coding different fixes for this bug weren't a complete waste. I've been able to reuse some of that code to optimize the recovery process. Now, rather than going through the mirror from front to back, it skips ahead to recover regions that have pending writes. Bottom line: performance will be bad during recovery, but it will be better than RHEL4.5. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cmirror-kernel/src/dm-cmirror-client.c.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.1.2.52&r2=1.1.2.53 http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cmirror-kernel/src/dm-cmirror-common.h.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.1.2.14&r2=1.1.2.15 http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cmirror-kernel/src/dm-cmirror-server.c.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.1.2.38&r2=1.1.2.39
next reply other threads:[~2007-09-26 3:15 UTC|newest] Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-09-26 3:15 jbrassow [this message] -- strict thread matches above, loose matches on Subject: below -- 2007-10-03 19:02 jbrassow 2007-09-27 20:31 jbrassow 2007-09-21 20:07 jbrassow 2007-09-13 15:24 jbrassow 2007-07-11 16:18 jbrassow 2007-04-26 16:55 jbrassow 2007-04-26 16:54 jbrassow 2007-04-24 20:10 jbrassow 2007-04-24 20:08 jbrassow 2007-04-10 7:13 jbrassow 2007-04-10 7:12 jbrassow 2007-04-05 21:33 jbrassow 2007-04-05 21:32 jbrassow 2007-04-03 18:23 jbrassow 2007-04-03 18:21 jbrassow 2007-03-22 22:34 jbrassow 2007-03-22 22:22 jbrassow 2007-03-14 4:28 jbrassow 2007-02-26 17:38 jbrassow 2007-02-20 19:35 jbrassow 2007-02-19 16:29 jbrassow 2007-02-14 17:44 jbrassow 2007-02-02 17:22 jbrassow 2007-01-08 19:28 jbrassow 2006-12-07 18:58 jbrassow 2006-09-05 17:50 jbrassow 2006-09-05 17:48 jbrassow 2006-07-27 23:11 jbrassow 2006-07-27 23:11 jbrassow 2006-07-22 22:19 jbrassow 2006-07-22 22:19 jbrassow 2006-07-22 22:12 jbrassow 2006-06-29 19:49 jbrassow 2006-06-29 19:48 jbrassow 2006-06-29 19:46 jbrassow 2006-06-27 20:19 jbrassow 2006-06-15 19:48 jbrassow 2006-06-15 19:34 jbrassow 2006-06-13 16:26 jbrassow 2006-06-02 22:04 jbrassow 2006-05-15 16:26 jbrassow 2006-02-08 21:59 jbrassow 2006-02-08 16:03 jbrassow 2006-02-06 23:04 jbrassow 2006-02-06 22:58 jbrassow 2006-02-06 18:14 jbrassow 2005-10-27 21:27 jbrassow 2005-10-27 11:03 jbrassow 2005-08-11 18:26 jbrassow 2005-07-28 22:53 jbrassow
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=20070926031541.29694.qmail@sourceware.org \ --to=jbrassow@sourceware.org \ --cc=cluster-cvs@sources.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: linkBe 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).