From: Artem Bityutskiy <dedekind1@gmail.com>
To: David Jander <david.jander@protonic.nl>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS on kernel 2.6.24?
Date: Wed, 09 Dec 2009 12:55:09 +0200 [thread overview]
Message-ID: <1260356109.19669.1289.camel@localhost> (raw)
In-Reply-To: <200912091140.03345.david.jander@protonic.nl>
On Wed, 2009-12-09 at 11:40 +0100, David Jander wrote:
> Back on topic:
> I have repeated the nand-tests on another board, and they ran just fine,
> repeating for quite a while without any error, so I guess that proves that the
> hardware and nand-driver are working reasonably well. OTOH, The two failed
> systems, also were running for several months with very heavy flash-disk I/O
> (not as much as to wear it out though, there's still roughly 40% free space on
> the UBI volume). It has gone through installing ubuntu on it, and building
> several debian packages from source, etc... all apparently without problems,
> until one day 'ls -l /etc/' just failed.
> I will try to pull from ubifs-v2.6.24.git, but I'd like to know your opinion
> on what the chances are that this update will fix the problem or bug that
> caused this corruption?
I cannot tell for sure, it may.
What I can say for sure is that I personally is not very interested in
solving problems for too old UBIFS code-base. Well, problems I can
reproduce here, in my setup, are OK, but subtle problems which I cannot
reproduce here are not OK - I really want to be sure UBI/UBIFS are
up-to-date and this is not something we already fixed.
BTW, from now on 2.6.24 back-port support is dropped. But it is
up-to-date _now_ :-)
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2009-12-09 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 14:10 UBIFS on kernel 2.6.24? David Jander
2009-11-26 7:23 ` Artem Bityutskiy
2009-12-08 16:45 ` David Jander
2009-12-09 8:41 ` Artem Bityutskiy
2009-12-09 10:40 ` David Jander
2009-12-09 10:55 ` Artem Bityutskiy [this message]
2009-12-10 9:19 ` David Jander
2009-12-10 9:23 ` Artem Bityutskiy
2009-12-11 11:42 ` Fortini Matteo
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=1260356109.19669.1289.camel@localhost \
--to=dedekind1@gmail.com \
--cc=david.jander@protonic.nl \
--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.