From: Iwo Mergler <iwo@call-direct.com.au>
To: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: Looks like a UBIFS bug... - Solved
Date: Thu, 03 Dec 2009 17:04:58 +1100 [thread overview]
Message-ID: <4B17550A.7010409@call-direct.com.au> (raw)
In-Reply-To: <4B173FC4.5020901@call-direct.com.au>
Iwo Mergler wrote:
> Iwo Mergler wrote:
>> Hi all,
>>
>> I've got some weird UBIFS-related behaviour. I'd welcome
>> any suggestions.
>>
Turns out that the same script that was erasing the partition,
creating ubifs, etc. was invoked a second time in the background.
I can't blame UBIFS for not surviving some random FLASH erasure
during operation. :-)
Sorry about the noise.
Iwo
next prev parent reply other threads:[~2009-12-03 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 4:22 Looks like a UBIFS bug Iwo Mergler
2009-12-03 4:34 ` Iwo Mergler
2009-12-03 6:04 ` Iwo Mergler [this message]
2009-12-03 7:33 ` Looks like a UBIFS bug... - Solved 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=4B17550A.7010409@call-direct.com.au \
--to=iwo@call-direct.com.au \
--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