From: Goldwyn Rodrigues <rgoldwyn@suse.com>
To: David Teigland <teigland@redhat.com>, Neil Brown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: clustered MD
Date: Sun, 14 Jun 2015 17:19:31 -0500 [thread overview]
Message-ID: <557DFDF3.2060106@suse.com> (raw)
In-Reply-To: <20150612184623.GA5130@redhat.com>
On 06/12/2015 01:46 PM, David Teigland wrote:
> When a node fails, its dirty areas get special treatment from other nodes
> using the area_resyncing() function. Should the suspend_list be created
> before any reads or writes from the file system are processed by md? It
> seems to me that gfs journal recovery could read/write to dirty regions
> (from the failed node) before md was finished setting up the suspend_list.
> md could probably prevent that by using the recover_prep() dlm callback to
> set a flag that would block any i/o that arrived before the suspend_list
> was ready.
>
> .
Yes, we should call mddev_suspend() in recover_prep() and mddev_resume()
after suspend_list is created. Thanks for pointing it out.
--
Goldwyn
next prev parent reply other threads:[~2015-06-14 22:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 18:22 clustered MD David Teigland
2015-06-09 19:26 ` Goldwyn Rodrigues
2015-06-09 19:45 ` David Teigland
2015-06-09 20:08 ` Goldwyn Rodrigues
2015-06-09 20:30 ` David Teigland
2015-06-09 20:33 ` David Lang
2015-06-10 3:33 ` Goldwyn Rodrigues
2015-06-10 8:00 ` Richard Weinberger
2015-06-10 13:59 ` Goldwyn Rodrigues
2015-06-10 15:01 ` David Teigland
2015-06-10 15:27 ` Goldwyn Rodrigues
2015-06-10 15:48 ` David Teigland
2015-06-10 16:23 ` Goldwyn Rodrigues
2015-06-10 17:05 ` David Teigland
2015-06-10 19:22 ` David Teigland
2015-06-10 20:31 ` Neil Brown
2015-06-10 21:07 ` David Teigland
2015-06-10 22:11 ` David Teigland
2015-06-10 22:50 ` Neil Brown
2015-06-12 18:46 ` David Teigland
2015-06-14 22:19 ` Goldwyn Rodrigues [this message]
2015-06-23 1:34 ` NeilBrown
2015-06-09 20:14 ` Goldwyn Rodrigues
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=557DFDF3.2060106@suse.com \
--to=rgoldwyn@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=teigland@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.