From: Jamie Lokier <jamie@shareable.org>
To: Jon Ringle <jon@ringle.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Erase race?
Date: Tue, 20 Apr 2010 23:00:07 +0100 [thread overview]
Message-ID: <20100420220007.GP11723@shareable.org> (raw)
In-Reply-To: <z2z152584231004201324tc69525a0hb86ff9fdeb679ca4@mail.gmail.com>
Jon Ringle wrote:
> On Tue, Apr 13, 2010 at 4:15 PM, Jon Ringle <jon@ringle.org> wrote:
> > Hi,
> > I have a few machines that have UBI and UBIFS on NOR flash that are
> > undergoing continuous reboot testing.
> > One of them just caught the following failure:
> >
> > [ 51.250000] IXP4XX-Flash.0: buffer write error (status 0xd0)
> > [ 51.250000] UBI error: ubi_io_write: error -22 while writing 64
> > bytes to PEB 226:0, written 0 bytes
> > [ 51.270000] UBI error: erase_worker: failed to erase PEB 226, error -22
> > [ 51.270000] UBI warning: ubi_ro_mode: switch to read-only mode
> > [ 51.290000] UBI error: do_work: work failed with error code -22
> > [ 51.290000] UBI error: ubi_thread: ubi_bgt0d: work failed with error code -22
> >
> > Looking at this it appears that the failure might have been caused due
> > to the erase_worker and ubi_io_write occurring out of order... since
> > it looks like ubi_io_write was trying to write at offset 0 of the PEB,
> > which I imagine would have to be the EC header, which should happen
> > after the block is erased. But it doesn't seem to be the case here.
>
> I had this issue occur again on another system:
> [ 48.250000] IXP4XX-Flash.0: buffer write error (status 0xd0)
> [ 48.250000] UBI error: ubi_io_write: error -22 while writing 64
> bytes to PEB 111:0, written 0 bytes
> [ 48.280000] UBI error: erase_worker: failed to erase PEB 111, error -22
> [ 48.280000] UBI warning: ubi_ro_mode: switch to read-only mode
> [ 48.310000] UBI error: do_work: work failed with error code -22
> [ 48.310000] UBI error: ubi_thread: ubi_bgt0d: work failed with error code -22
>
> Can anyone comment as to my theory that this is a race condition
> between ubi_io_write and erase_worker occurring out of order?
I have nothing to offer, but I'm interested in anything more you
discover as I would like to use UBIFS on NOR too.
-- Jamie
next prev parent reply other threads:[~2010-04-20 22:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 20:15 Erase race? Jon Ringle
2010-04-20 20:24 ` Jon Ringle
2010-04-20 22:00 ` Jamie Lokier [this message]
2010-04-27 12:59 ` Artem Bityutskiy
2010-05-12 2:30 ` Jon Ringle
2010-05-12 3:32 ` Artem Bityutskiy
2010-05-12 8:21 ` massimo cirillo
2010-05-12 12:00 ` Jon Ringle
2010-05-12 12:31 ` massimo cirillo
2010-05-13 13:23 ` Jon Ringle
2010-04-20 23:04 ` 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=20100420220007.GP11723@shareable.org \
--to=jamie@shareable.org \
--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 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.