From: "Paul Wong" <paul.wong@digitalview.com>
To: <linux-mtd@lists.infradead.org>
Subject: jffs2 filesystem
Date: Wed, 18 Sep 2002 11:53:43 +0800 [thread overview]
Message-ID: <005601c25ec7$0b5f8f30$9000010a@paulwong> (raw)
Hi! all,
I have a problem about the jffs2 file system. Pls. refer below message.
If the i/o error occur in eraseall process, is the jffs2 fs corrupted if i
copy the jffs2 image to /dev/mtd1 ? Does the "dd" or "cp" take care the i/o
error? thanks.
Paul
****************************************************************************
***
bash-2.04# eraseall /dev/mtd1
Erasing 16 Kibyte @ f0000 -- 9 % compnand_erase: attempt to erase a bad
block a
t page 0x00003d20
Erasing 16 Kibyte @ 1a4000 -- 16 % complete.
eraseall: /dev/mtd1: MTD Erase failure: Input/output error
Erased 10240 Kibyte @ 0 -- 100% complete.
bash-2.04# dd if=jffs2.img of=/dev/mtd1 bs=1k
dd: writing `/dev/mtd1': Bad address
3607+1 records in
3607+0 records out
bash-2.04#
****************************************************************
next reply other threads:[~2002-09-18 3:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 3:53 Paul Wong [this message]
2002-09-18 6:05 ` jffs2 filesystem Thomas Gleixner
2002-09-18 8:04 ` paul
2002-09-18 8:46 ` 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='005601c25ec7$0b5f8f30$9000010a@paulwong' \
--to=paul.wong@digitalview.com \
--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