public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: David Jander <david.jander@protonic.nl>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
	Adrian Hunter <adrian.hunter@nokia.com>
Subject: Re: Good stress test for UBIFS?
Date: Thu, 07 Jan 2010 09:17:03 +0200	[thread overview]
Message-ID: <1262848623.21915.45.camel@localhost> (raw)
In-Reply-To: <201001061159.59875.david.jander@protonic.nl>

On Wed, 2010-01-06 at 11:59 +0100, David Jander wrote:
> On Monday 28 December 2009 11:40:43 am Adrian Hunter wrote:
> >[...]
> > Generally we test with debugging checks turned on because they will spot an
> > error the instant it happens.  On the other hand, you must also test the
> >  actual configuration you will deploy.
> > 
> > There are two approaches.  We use both of them.  They are:
> > 
> > 1. Set up a desktop machine with your kernel and test on nandsim.  This has
> >  the advantage that it can do very many more operations than a small
> >  device.
> > 
> > You can simulate power-off-recovery by using UBIFS "failure mode".  Set
> >  UBIFS debugging module parameter debug_tsts to 4.  There is a script I
> >  have used for that below.
> 
> Yes, but I did not consider this option, because it is a completely different 
> processor architecture (little-endian vs. big-endian), also it won't test the 
> hardware-driver, nor the nand-chip and interface which can potentially also be 
> (part of) the problem. Here I am trying to reproduce a situation that has 
> already occurred a few times in "real life", and I need to be sure it won't 
> happen ever again with the latest ubi/ubifs.
> 
> > 2. Run tests on the device.  There are tests in mtd-utils/tests/fs-tests
> >  but LTP's fsstress is good for stressing the file system during
> >  power-off-recovery testing.
> 
> Thanks a lot. I will try fsstress.
> I had already written my own test script, mimicking some suspicious scenarios, 
> in the hope it would reproduce what had happend on three of our boards 
> (corrupt fs), and eventually succeded, but it took several days running.
> Now I am re-running the test with latest UBI/UBIFS to see if it's gone.
> Hopefully fsstress will yield results more quickly.

Also, take a look at the MTD tests:

http://www.linux-mtd.infradead.org/doc/general.html#L_mtd_tests

E.g., by running the torture test for a week we once found a very rare
and subtle problem in our OneNAND driver related to the DMA transfers.
Also, it is nice to run this test for few months and see how your NAND
HW behaves when you try to wear few of their blocks out. Also, if you
manage to make real faulty blocks, you can test how UBI handles them.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2010-01-07  7:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18  8:00 Good stress test for UBIFS? David Jander
2009-12-28 10:40 ` Adrian Hunter
2010-01-06 10:59   ` David Jander
2010-01-07  7:17     ` Artem Bityutskiy [this message]
2010-01-07 10:38       ` david

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=1262848623.21915.45.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=adrian.hunter@nokia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox