From: Artem Bityutskiy <dedekind1@gmail.com>
To: Matthieu CASTET <matthieu.castet@parrot.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
Adrian Hunter <adrian.hunter@nokia.com>
Subject: Re: ubifs: sync() causes writes even if nothing is changed
Date: Thu, 21 Oct 2010 21:43:29 +0300 [thread overview]
Message-ID: <1287686609.7480.0.camel@brekeke> (raw)
In-Reply-To: <4CC0729B.7060109@parrot.com>
On Thu, 2010-10-21 at 19:04 +0200, Matthieu CASTET wrote:
> Hi,
>
> Artem Bityutskiy a écrit :
> > On Thu, 2010-10-21 at 10:23 +0200, Sebastian Andrzej Siewior wrote:
> >> Artem Bityutskiy wrote:
> >>>> From a quick glance at the ubifs code, this might come out of the
> >>>> garbage collector that is triggered on every sync() and writes
> >>>> something even if nothing has changed.
> >
> > Yeah, the UBIFS must be writing the commit start and commit end nodes,
> > and then erasing the previous log LEB (all this is done in log.c). As
> > soon as I have time I'll look at this, I really do not have time right
> > now. And there is Matthiew's problem which is actually quite big, but
> > for some reasons affects only him :-)
> It could be interesting to know which nand flash are tested.
>
> On our boards ST 256MB chip work fine, but micron flash got unstable
> page problem (sorry I don't have the model number ATM).
>
> And it is getting worse, new SLC flash can now get up to 4 bits error
> per 512.
It would be great if you sent me a board where unstable pages are easy
to reproduce.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2010-10-21 18:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 16:30 ubifs: sync() causes writes even if nothing is changed Hans J. Koch
2010-10-15 6:13 ` Artem Bityutskiy
2010-10-20 13:26 ` Artem Bityutskiy
2010-10-21 8:23 ` Sebastian Andrzej Siewior
2010-10-21 8:32 ` Artem Bityutskiy
2010-10-21 17:04 ` Matthieu CASTET
2010-10-21 18:43 ` Artem Bityutskiy [this message]
2011-01-16 17:48 ` Artem Bityutskiy
2011-01-17 8:19 ` Adrian Hunter
2011-01-17 9:04 ` Artem Bityutskiy
2011-01-17 21:52 ` Artem Bityutskiy
2011-01-17 21:53 ` [PATCH v2 1/3] UBIFS: re-arrange variables in ubifs_info Artem Bityutskiy
2011-01-17 21:54 ` [PATCH v2 2/3] UBIFS: introduce mounting flag Artem Bityutskiy
2011-01-18 7:30 ` [PATCH v2 3/3] UBIFS: do not start the commit if there is nothing to commit Artem Bityutskiy
2011-01-18 7:36 ` Artem Bityutskiy
2011-01-18 12:29 ` John Ogness
2011-01-21 11:13 ` Artem Bityutskiy
2011-01-21 11:28 ` John Ogness
2011-01-25 8:20 ` 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=1287686609.7480.0.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=adrian.hunter@nokia.com \
--cc=linux-mtd@lists.infradead.org \
--cc=matthieu.castet@parrot.com \
/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).