From: Alexander Pazdnikov <pazdnikov@prosoft.ural.ru>
To: <linux-mtd@lists.infradead.org>, Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: ubifs became broken on contigous power-fails
Date: Tue, 15 Jun 2010 11:02:01 +0600 [thread overview]
Message-ID: <201006151102.01851.pazdnikov@prosoft.ural.ru> (raw)
In-Reply-To: <1276352575.19028.121.camel@localhost>
В сообщении от Суббота 12 июня 2010 20:22:55 автор Artem Bityutskiy написал:
> On Mon, 2010-05-24 at 12:56 +0300, Artem Bityutskiy wrote:
> > On Mon, 2010-05-24 at 15:50 +0600, Alexander Pazdnikov wrote:
> > > > Could you enable debugging messages when mounging it after power
> > > > cuts? The messages generate a lot of noise, so you need to disable
> > > > them before starting the real test. The idea is to get UBIFS
> > > > debugging messages when errors occur.
> > >
> > > Sorry, I've hurried up, and after applying your pathes reflash all of
> > > the devices with new firmware.
> > > But I'll setup some devices with all firmware to catch this issue
> > > again.
> > >
> > > > I never had time to really dig this and fix. Would be nice if you
> > > > could do this because I will unlikely have time in the nearest
> > > > future, but I can help you.
> > >
> > > Thank you, I'll continue testings and can supply with debug
> > > information.
> > >
> > > > One think you can do is to make sure you do not fill UBIFS
> > > > completely, then you will avoid hitting these budgeting bugs, also
> > > > known as ENOSPC issues (I think btrfs uses this terminology).
> > >
> > > In the issue above there is 11% used space and 89% free space.
> > > I've got this issue only when mounting fs in RO and then remounting it
> > > in RW.
> >
> > OK. Try my patch. Also, it is worth running your tests with UBIFS extra
> > self checks enabled.
>
> Did it help?
>
Artem, thank you very much, yes - it helped, all of 10 testing devices
survived with repeatable powerfails (1,2,3,4,5,6,7,8,9,10 minutes in this
sequence) for a week.
Now we leave 3 devices for this test.
Appologize me, please, I've not tested again for the RO-RW recovery on remount
with this patch to supply you with debug info.
--
Best Regards,
Alexander Pazdnikov
next prev parent reply other threads:[~2010-06-15 5:01 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
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 [this message]
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=201006151102.01851.pazdnikov@prosoft.ural.ru \
--to=pazdnikov@prosoft.ural.ru \
--cc=dedekind1@gmail.com \
--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).