From: "Simon Haynes" <simon@baydel.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 Corruption.
Date: Thu, 26 Feb 2004 11:08:16 -0000 [thread overview]
Message-ID: <403DD3A0.4494.196896@localhost> (raw)
In-Reply-To: <1077704741.11584.953.camel@imladris.demon.co.uk>
On 25 Feb 2004 at 10:25, David Woodhouse wrote:
> On Wed, 2004-02-25 at 09:49 +0000, simon@baydel.com wrote:
> > As I do mount read only on shutdown I assume this is corruption ?
>
> Maybe. I doubt it's _harmful_ but I am very interested.
>
This has taken some time to produce. I have a 40Mb logfile which thankfully
compresses to 4Mb. To generate the log I booted the system via the network with
JFFS2 patched to use /dev/ram MAJOR, but no JFFS2 debug. I erased the SMC and
made a clean JFFS2 filesystem. I then copied all of my root files. I mounted and
umounted this a few times and each time I created and deleted a few files. I did not
get one error.
I then rebooted using a similar kernel with CONFIG_JFFS2_FS_DEBUG=1 and
passed arguments "root=/dev/ram1 debug".
It took about 6 hours before I could log in. I then halted the system. On the first
reboot, fortunately, I did get a CRC error but I cannot find where this was previously
written. The node is 0x000303f0.
I also observe the Empty flash XXXX ends at XXX. Which do not appear before the
filesystem is used as rootfs and restarted.
Beyond that I don't really know what I am looking for in the log. I can mail it to you
personally but as I said it's 4Mb compressed.
Cheers
Simon.
__________________________
Simon Haynes - Baydel
Phone : 44 (0) 1372 378811
Email : simon@baydel.com
__________________________
next prev parent reply other threads:[~2004-02-26 11:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 16:48 JFFS2 Corruption simon
2004-02-23 11:07 ` simon
2004-02-24 9:48 ` simon
2004-02-24 12:00 ` David Woodhouse
2004-02-24 12:54 ` Simon Haynes
2004-02-24 13:04 ` Simon Haynes
2004-02-24 13:40 ` Simon Haynes
2004-02-24 14:22 ` David Woodhouse
2004-02-24 14:25 ` Simon Haynes
2004-02-24 14:56 ` David Woodhouse
2004-02-24 14:58 ` Simon Haynes
2004-02-24 15:35 ` David Woodhouse
2004-02-24 15:47 ` Simon Haynes
2004-02-24 16:14 ` David Woodhouse
2004-02-24 16:17 ` Simon Haynes
2004-02-24 16:51 ` David Woodhouse
2004-02-24 17:05 ` Simon Haynes
2004-02-24 18:05 ` David Woodhouse
2004-02-24 18:04 ` Simon Haynes
2004-02-25 9:49 ` simon
2004-02-25 10:25 ` David Woodhouse
2004-02-26 11:08 ` Simon Haynes [this message]
2004-02-26 11:55 ` David Woodhouse
2004-03-03 15:31 ` David Woodhouse
2004-03-08 15:10 ` Simon Haynes
2004-03-09 15:33 ` Simon Haynes
2004-03-16 16:14 ` David Woodhouse
2004-03-19 10:37 ` Simon Haynes
2004-03-19 11:11 ` David Woodhouse
2004-02-24 17:12 ` Simon Haynes
2004-02-24 16:55 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2004-02-05 13:15 JFFS2 corruption Florian Schirmer
2004-02-08 10:37 ` David Woodhouse
2004-02-08 11:38 ` Florian Schirmer
2004-02-08 11:53 ` David Woodhouse
2004-02-08 17:02 ` Florian Schirmer
2004-02-08 17:13 ` David Woodhouse
2004-02-08 11:28 ` David Woodhouse
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=403DD3A0.4494.196896@localhost \
--to=simon@baydel.com \
--cc=dwmw2@infradead.org \
--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