From: "Gad Hayisraeli" <gad@syete.co.il>
To: <justin.wojdacki@analog.com>
Cc: "Linux - MTD list" <linux-mtd@lists.infradead.org>
Subject: Re: Fw: jffs2 crc errors
Date: Sun, 9 Jun 2002 11:37:06 +0200 [thread overview]
Message-ID: <006f01c20f99$38780d80$1900000a@v.vmanage.com> (raw)
In-Reply-To: 3CFFA37C.F222E9E0@analog.com
----- Original Message -----
From: "Justin Wojdacki" <justin.wojdacki@analog.com>
To: "Gad Hayisraeli" <gad@syete.co.il>
Cc: "Linux - MTD list" <linux-mtd@lists.infradead.org>
Sent: Thursday, June 06, 2002 8:01 PM
Subject: Re: Fw: jffs2 crc errors
> Gad Hayisraeli wrote:
> >
> > > i encounter this err in boot:
> > >
> > > jffs2_scan_inode_node(): Data CRC failed on node at 0x001eaa24: Read
> > > 0xda7b03c2,
> > > calculated 0x0da9fb30
> > >
> > > and it keeps appearing every boot.
> > >
> > > is it bad ?
> > >
> > > maybe its not fixed becuse i'm terminating the jffs optimization
thread in
> > > the middle of the init process ?
> > >
> > > thanks
> > >
> > > Gad
> >
>
> Well, this could mean that the sector the node is in is going bad
> (which would be a bad thing for you). Or it could mean that the write
> process didn't complete, and so the calculated CRC is coming off of
> stale data.
>
> Why are you killing off the optimization thread?
>
this bad thread is making me nuts , because its slowers the FS alot !
David Woodhouse suggested it for me.
now i'm asking if it hurts to kill it (BTW i cannot kill it but the most i
can do it to stop it) ?
(especially in relation to this bad crc errs)
thanks
Gad
prev parent reply other threads:[~2002-06-09 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 17:48 Fw: jffs2 crc errors Gad Hayisraeli
2002-06-06 18:01 ` Justin Wojdacki
2002-06-09 9:37 ` Gad Hayisraeli [this message]
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='006f01c20f99$38780d80$1900000a@v.vmanage.com' \
--to=gad@syete.co.il \
--cc=justin.wojdacki@analog.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