linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Pazdnikov <pazdnikov@prosoft.ural.ru>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: ubifs became broken on contigous power-fails
Date: Wed, 19 May 2010 16:36:21 +0600	[thread overview]
Message-ID: <201005191636.21845.pazdnikov@prosoft.ural.ru> (raw)
In-Reply-To: <201005131408.01573.pazdnikov@prosoft.ural.ru>

В сообщении от Четверг 13 мая 2010 14:08:01 автор Alexander Pazdnikov написал:
> We've separated EC and VID headers to different pages, setuped 4 devices on
> test run.

We've setuped 5 devices with EC and VID headers in one page (data offset = 
2048) and 5 devices with EC and VID headers in separate pages (data offset = 
4096).

On all devices the filesystem can became broken.

But a strange thing we've admited. If FS became broken then mounting it by 
hand at boot time in RO mode and then remounting in RW mode repairs the 
filesystem and an assertion and the following 
error disappears:

UBIFS error (pid 462): ubifs_rcvry_gc_commit: could not find a dirty LEB

UBIFS error (pid 495): ubifs_leb_unmap: unmap LEB -1 failed, error -22


Any advices, please.

--
Best regards,
Sasha

  reply	other threads:[~2010-05-19 10:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11 14:43 ubifs became broken on contigous power-fails Alexander Pazdnikov
2010-05-12  7:30 ` Alexander Pazdnikov
2010-05-13  8:08   ` Alexander Pazdnikov
2010-05-19 10:36     ` Alexander Pazdnikov [this message]
2010-05-20 13:18       ` Alexander Pazdnikov
2010-05-23 11:28 ` Artem Bityutskiy
2010-05-23 12:23   ` Artem Bityutskiy
2010-05-24  6:49     ` Alexander Pazdnikov
2010-05-24  8:18       ` Artem Bityutskiy
2010-05-24  9:50         ` Alexander Pazdnikov
2010-05-24  9:56           ` Artem Bityutskiy
2010-06-12 14:22             ` Artem Bityutskiy
2010-06-15  5:02               ` Alexander Pazdnikov
2010-07-13  3:58                 ` Artem Bityutskiy

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=201005191636.21845.pazdnikov@prosoft.ural.ru \
    --to=pazdnikov@prosoft.ural.ru \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pazdnikov@prosoftsystems.ru \
    /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).