From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guoqing Jiang Subject: Re: [PATCH 3/3] Safeguard against writing to an active device of another node Date: Thu, 30 Jul 2015 16:38:32 +0800 Message-ID: <55B9E288.7060002@suse.com> References: <1436172732-21021-1-git-send-email-gqjiang@suse.com> <1436172732-21021-3-git-send-email-gqjiang@suse.com> <20150729172853.33d44808@noble> <55B8ADE1.1060708@suse.com> <20150730080247.20f03d23@noble> <55B99709.2050609@suse.com> <55B9DEBB.4040403@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <55B9DEBB.4040403@suse.com> Sender: linux-raid-owner@vger.kernel.org To: NeilBrown Cc: rgoldwyn@suse.de, linux-raid@vger.kernel.org List-Id: linux-raid.ids Guoqing Jiang wrote: > Guoqing Jiang wrote: > >> Hi Neil, >> >> >>> Probably something like that - yes. Unfortunately your mailer messed >>> that up more that usual make it rather difficult to apply. >>> >>> >>> >>> >> Sorry, it is just for review. >> >> >>> I was wondering if we could make it a run-time dependency though .. a >>> bit like get_cluster_name. We can still do that later I guess. I'm >>> not really sure what is best at the moment. >>> >>> >>> >>> >> It could be, I am changing it and run some test, then the new version patch >> will be send. >> >> > After change to dynamic load dlm library, if compile mdadm without > related dlm library, > then some problems appeared, such as unlock dlm would fail when create > cluster-md, > the errno is 52 (EBADE: Invalid exchange). > > But, if compile mdadm with previous code, then nothing wrong happened > whether > the dlm library is installed or not. > > Oops, if dlm library is not existed then the dlm code is not even compiled in previous code, so it doesn't complain about anything about dlm. Thanks, Guoqing