All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fredrick Prashanth John Berchmans <fredrickprashanth@gmail.com>
To: dwmw2@infradead.org
Cc: linux-mtd@lists.infradead.org, Suresh Siddha <sbsiddha@gmail.com>
Subject: 
Date: Thu, 25 Feb 2016 17:19:20 -0800	[thread overview]
Message-ID: <CACwgvgU05i7-72bgWeY3uAx1DFotJ2j3zBz2wDz3-ujeGBm6aQ@mail.gmail.com> (raw)

Hi,

We are using UBIFS on our NOR flash.
We are observing that a lot of times the filesystem goes to read-only
unable to recover.
Most of the time its due to
a) ubifs_scan_a_node failing due to bad crc or unclean free space.
b) ubifs_leb_write failing to erase due to erase timeout

[ The above would have happened due to unclean power cuts. In our
environment this happens often ]

I checked the code in jffs2. Looking at jffs2 code it looks like jffs2
tolerates the above two
failures and moves on without mounting read-only.
Is my understanding right ?

Could we change the ubifs_scan_a_node to skip corrupted bytes and move
to next node,
instead of returning error ?


Thanks,
Fredrick

             reply	other threads:[~2016-02-26  1:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26  1:19 Fredrick Prashanth John Berchmans [this message]
2016-02-26  7:37 ` Richard Weinberger

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=CACwgvgU05i7-72bgWeY3uAx1DFotJ2j3zBz2wDz3-ujeGBm6aQ@mail.gmail.com \
    --to=fredrickprashanth@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sbsiddha@gmail.com \
    /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.