From: Artem Bityutskiy <dedekind@infradead.org>
To: Jason Liu <liu.h.jason@gmail.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>,
Adrian Hunter <adrian.hunter@nokia.com>
Subject: Re: ubifs error when do bonnie++ test
Date: Tue, 14 Apr 2009 09:17:54 +0300 [thread overview]
Message-ID: <1239689874.3390.88.camel@localhost.localdomain> (raw)
In-Reply-To: <e8775dd00904122350h23a9983axd507c88f283150f@mail.gmail.com>
On Mon, 2009-04-13 at 14:50 +0800, Jason Liu wrote:
> 2009/4/10 Artem Bityutskiy <dedekind@infradead.org>:
> > On Thu, 2009-04-02 at 17:49 +0800, Jason Liu wrote:
> >> 2009/4/2 Adrian Hunter <adrian.hunter@nokia.com>:
> >> > Jason Liu wrote:
> >> >>
> >> >> I'm working on the 2.6.26 with ubifs enabled, but after some stress
> >> >> test, ubifs give some err. The following is the steps to reproduce.
> >> >
> >> > Please apply all recent UBIFS patches and enable debugging and try
> >> > again.
> >> >
> >> > You could also enable debugging checks, but that will really slow it down.
> >> >
> >> >
> >> After apply all the patches from users/dedekind/ubifs-v2.6.26.git
> >> I still get errors with bonnie++ test and only run 3times compared 390
> >> times without the patch
> >>
> >> Using uid:0, gid:0.
> >> Writing with putc()...done
> >> Writing intelligently...done
> >> Rewriting...done
> >> Reading with getc()...done
> >> Reading intelligently...done
> >> start 'em...done...done...done...
> >> Create files in sequential order...done.
> >> Stat files in sequential order...Expected 16384 files but only got 16385
> >> Cleaning up test directory after error.
> >
> > So have you tried to enable UBIFS extra checks?
> Yes, The test is in progress. It's really slow after enable UBIFS
> debug and extra checks.It will cost half hour for one test.And the
> test case failed without debug off after 600 round of test.So it will
> cost 600 * 0,5 = 300 hours with debug on, longer than 10 days.
When you reproduce this, please, do not forget to type dmesg
and save the output. Also, it is good idea to save an image
of your flash.
Could you please tell what is your flash device? I see this:
UBI: physical eraseblock size: 1048576 bytes (1024 KiB)
UBI: logical eraseblock size: 1032192 bytes
UBI: smallest flash I/O unit: 8192
UBI: VID header offset: 8192 (aligned 8192)
UBI: data offset: 16384
So your flash have huge PEB size of 1MiB. Min I/O unit size is
also huge - 8KiB. And no sub-pages. What is this device? Some
kind of NAND?
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-04-14 6:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 5:44 ubifs error when do bonnie++ test Jason Liu
2009-04-02 8:07 ` Adrian Hunter
2009-04-02 9:49 ` Jason Liu
2009-04-02 12:12 ` Adrian Hunter
2009-04-02 12:25 ` Artem Bityutskiy
2009-04-10 12:27 ` Artem Bityutskiy
2009-04-13 6:50 ` Jason Liu
2009-04-14 6:17 ` Artem Bityutskiy [this message]
2009-04-15 8:44 ` Jason Liu
2009-04-15 8:50 ` Artem Bityutskiy
2009-04-15 8:51 ` Artem Bityutskiy
2009-04-15 8:55 ` 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=1239689874.3390.88.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=adrian.hunter@nokia.com \
--cc=linux-mtd@lists.infradead.org \
--cc=liu.h.jason@gmail.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