linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jon Ringle <jon@ringle.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: fsck.ubifs?
Date: Tue, 09 Feb 2010 13:52:04 +0200	[thread overview]
Message-ID: <1265716324.2006.133.camel@localhost> (raw)
In-Reply-To: <152584231002010817n765ffd96j7f628d1f23a84b7c@mail.gmail.com>

On Mon, 2010-02-01 at 11:17 -0500, Jon Ringle wrote:
> I have my ubi0 partitioned with two static volumes: kernel and
> squashfs, and one dynamic volume: ubifs.

OK.

> One of the tests that I do to test for recovery from corruption is
> perform a flash_erase on random blocks on the mtd device that ubi0 is
> on and reboot. During bootup, I am able to easily detect corruption in
> the static ubi volumes with the crc checksum and these images are
> automatically reflashed.

OK.

> However, if there is corruption in the ubifs, quite often ubifs mounts
> successfully and only when trying to access files are problems being
> reported. Is there any kind of fsck.ubifs type of utility that can be
> used to help with this problem?

Unfortunately we did not implement any fsck.ubifs.

In your situation, the easiest think to do is to try to read all files
in the FS and make sure they can be read.

In general, UBIFS is very recoverable FS, and it can recover from many
errors nicely, so that only minimum of data is lost. See the
"recoverability" part here:

http://www.linux-mtd.infradead.org/doc/ubifs.html#L_overview

But we did not implement any utility which could do this.

And I think it is much much easier to doe the recovery in the kernel.
Probably some mount option like 'recover' could be introduced to do
this. But again, we did not implement this.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

      reply	other threads:[~2010-02-09 11:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01 16:17 fsck.ubifs? Jon Ringle
2010-02-09 11:52 ` Artem Bityutskiy [this message]

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=1265716324.2006.133.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=jon@ringle.org \
    --cc=linux-mtd@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).