From: Artem Bityutskiy <dedekind1@gmail.com>
To: David Peverley <pev@sketchymonkey.com>
Cc: Karl Beldan <karl.beldan@gmail.com>, linux-mtd@lists.infradead.org
Subject: Re: Testing a device using mtd_stresstest
Date: Fri, 11 Feb 2011 17:16:02 +0200 [thread overview]
Message-ID: <1297437362.2760.57.camel@localhost> (raw)
In-Reply-To: <AANLkTikH6AtyN45Z7wA4tpaxXsLhGUnZZj=bpC18F=xn@mail.gmail.com>
On Fri, 2011-02-11 at 14:25 +0000, David Peverley wrote:
> Sometimes... When they are I've manually marked blocks as bad and
> re-started the test run :-D I had wondered about whether it was blocks
> naturally failing with use, but some of these blocks haven't been (Ok,
> SHOULDNT have been!) erased anywhere near 100,000 times so I'm
> suspicious about this. When I looked into it I noted that the
> mtd_stresstest.ko doesn't mark blocks as bad ever so this is
> potentially something that would occur.
Yeah, I think the tests should not do this, they should just test and
report you issues.
> However, nandtest.c in
> mtd-utils I notice *does* support marking of bad blocks during
> testing. Should I consider using this instead? I'm not sure what the
> relationship between these test tools is...?
These are tools wirtten by different people at different times. Kernel
MTD tests were written by Nokia guys and I think the tests are more or
less consistent in how they behave.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-02-11 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 12:12 Testing a device using mtd_stresstest David Peverley
2011-02-06 14:24 ` Artem Bityutskiy
2011-02-07 13:44 ` David Peverley
2011-02-07 14:01 ` Andrew Murray
2011-02-07 14:39 ` Arno Steffen
2011-02-10 15:24 ` David Peverley
2011-02-18 10:59 ` Arno Steffen
[not found] ` <AANLkTi=UgsLq3=7ma9MPJJBVxtNvyr=ThtLPy8qzC3Bk@mail.gmail.com>
2011-02-10 12:30 ` David Peverley
[not found] ` <AANLkTimJFv1Uy2c70ewPUHYH58rQHT=VsDa3ioU9hJZh@mail.gmail.com>
2011-02-11 14:25 ` David Peverley
2011-02-11 15:16 ` Artem Bityutskiy [this message]
2011-02-11 16:42 ` David Peverley
2011-02-11 15:12 ` 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=1297437362.2760.57.camel@localhost \
--to=dedekind1@gmail.com \
--cc=karl.beldan@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=pev@sketchymonkey.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 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.