From: Ben Dooks <ben@fluff.org.uk>
To: Lorenzo PARISI <lorenzo.parisi@st.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Benchmark errors
Date: Fri, 8 Oct 2004 11:00:02 +0100 [thread overview]
Message-ID: <20041008100002.GJ12218@home.fluff.org> (raw)
In-Reply-To: <83197f15.8bfe70e2.81c1800@mail1.agr.st.com>
On Fri, Oct 08, 2004 at 11:52:23AM +0200, Lorenzo PARISI wrote:
> Hi all,
>
> when I benchmark the NAND with Bonnie++, I receive many
> errors:
>
> nand_write_oob: Failed write verify, page 0x0....
> : : :
> : : :
>
> and Bonnie++ end with this messages:
>
> Bonnie: drastic I/O error (rmdir): Directory not empty
> Cleaning up test directory after error
> Bonnie: drastic I/O error (rmdir): No such file or directory
>
> Initially, I thinked that a problem of Bonnie++, but if I
> run Bonnie++ on a NAND with JFFS2, I don't receive any
> errors.
erm, what filesystem are you using the gives errors?
NAND is not guaranteed to be defectless, the fs must
be able to deal with bad blocks in the NAND.
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next prev parent reply other threads:[~2004-10-08 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 9:52 Benchmark errors Lorenzo PARISI
2004-10-08 10:00 ` Ben Dooks [this message]
2004-10-08 10:00 ` Thomas Gleixner
2004-10-08 10:27 ` Thomas Gleixner
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=20041008100002.GJ12218@home.fluff.org \
--to=ben@fluff.org.uk \
--cc=linux-mtd@lists.infradead.org \
--cc=lorenzo.parisi@st.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