From mboxrd@z Thu Jan 1 00:00:00 1970 From: Heiko Schocher Date: Sun, 18 Jan 2015 11:07:13 +0100 Subject: [U-Boot] Unreadable UBIFS partition after power cuts In-Reply-To: References: <150521CB44B50A4A98049E9C7BAFB0F30D9B823F@DETENEXMB01.delta.corp> <54B683DB.2030108@denx.de> <150521CB44B50A4A98049E9C7BAFB0F30D9B8760@DETENEXMB01.delta.corp> <54B76C26.6010809@denx.de> <150521CB44B50A4A98049E9C7BAFB0F30D9C15C8@DETENEXMB01.delta.corp> <87iog63f6r.fsf@nbsps.com> Message-ID: <54BB85D1.2030209@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hello Anton, Am 17.01.2015 17:06, schrieb Anton Habegger: > Now I realized the "dangling branch" and "dangling match" messages on > Linux is generated during the ubifs_replay_journal(). Under U-Boot > this call is disabled: > > super.c mount_ubifs: > > #ifndef __UBOOT__ > err = ubifs_replay_journal(c); > if (err) > goto out_journal; > #endif > > I'm unfortunately not an expert in UBIFS, but I'm wondering how can > U-Boot grantee to open a UBIFS volume after an power cut in a not > corrupted state without replaying the journal? > > Thank you to give me one hint again. Could you try to enable it? The necessary functions should be also in the U-Boot code, so this should be not to difficult ... Thanks! bye, Heiko -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany