All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Unreadable UBIFS partition after power cuts
Date: Sun, 18 Jan 2015 11:07:13 +0100	[thread overview]
Message-ID: <54BB85D1.2030209@denx.de> (raw)
In-Reply-To: <CANCpNELuRA7LBgqDevOSZdsJ4pKN6z-S6jvsi_saJHPNr=uv-Q@mail.gmail.com>

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

  reply	other threads:[~2015-01-18 10:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 12:52 [U-Boot] Unreadable UBIFS partition after power cuts Anton Habegger
2015-01-14 14:57 ` Heiko Schocher
2015-01-14 17:12   ` Anton Habegger
2015-01-15  7:28     ` Heiko Schocher
2015-01-16 15:10       ` Anton Habegger
2015-01-16 15:21         ` Anton Habegger
2015-01-16 15:42         ` Bill Pringlemeir
2015-01-16 17:47           ` Anton Habegger
2015-01-17 16:06             ` Anton Habegger
2015-01-18 10:07               ` Heiko Schocher [this message]
2015-01-19 11:29                 ` Anton Habegger
2015-01-20  7:26                   ` Heiko Schocher
  -- strict thread matches above, loose matches on Subject: below --
2015-01-16 15:38 Anton Habegger

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=54BB85D1.2030209@denx.de \
    --to=hs@denx.de \
    --cc=u-boot@lists.denx.de \
    /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.