From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga11.intel.com ([192.55.52.93]) by bombadil.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1ZtX1G-0002gw-Lo for linux-mtd@lists.infradead.org; Tue, 03 Nov 2015 08:32:44 +0000 Message-ID: <1446539539.6126.110.camel@gmail.com> Subject: Re: master node can not be recovered From: Artem Bityutskiy Reply-To: dedekind1@gmail.com To: Bean Huo =?UTF-8?Q?=E9=9C=8D=E6=96=8C=E6=96=8C?= "(beanhuo)" , "linux-mtd@lists.infradead.org" Cc: Richard Weinberger Date: Tue, 03 Nov 2015 10:32:19 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 2015-11-02 at 16:10 +0000, Bean Huo 霍斌斌 (beanhuo) wrote: > Hi, Richard > I tested my UBI power loss solution, have a question about master > node. > We all know that if master node be corrupted by power loss , we can > recover it by second one. But from my testing results, in fact, > It cannot be recovered by second backup master node. If first master > node be corrupted by power loss, this relevant block will be > correctly read, get_master_node will not reture 0, so next time > recover operation will not run. > Or I'm wrong? There are debugging messages, can you please try to enable them and share the resutl, so that we could see what was going on?