From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga01.intel.com ([192.55.52.88]) by bombadil.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1ZtXeB-0007XN-Kj for linux-mtd@lists.infradead.org; Tue, 03 Nov 2015 09:12:55 +0000 Message-ID: <1446541937.6126.125.camel@gmail.com> Subject: Re: master node can not be recovered From: Artem Bityutskiy Reply-To: dedekind1@gmail.com To: Richard Weinberger , Bean Huo =?UTF-8?Q?=E9=9C=8D=E6=96=8C=E6=96=8C?= "(beanhuo)" , "linux-mtd@lists.infradead.org" Date: Tue, 03 Nov 2015 11:12:17 +0200 In-Reply-To: <5637934D.5000503@nod.at> References: <5637934D.5000503@nod.at> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 2015-11-02 at 17:46 +0100, Richard Weinberger wrote: > ubifs_recover_master_node() is very strict. Just like the rest of the recovery code, the master node part is consistent with that. > Can it be that in your case more than the last written page is > corrupted? I suspect so too.