Fw: jffs2 crc errors

Fw: jffs2 crc errors

[Gad Hayisraeli]

> 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

Re: Fw: jffs2 crc errors

[Justin Wojdacki]

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? 

-- 
-------------------------------------------------
Justin Wojdacki        
justin.wojdacki@analog.com         (408) 350-5032
Communications Processors Group -- Analog Devices

Re: Fw: jffs2 crc errors

[Gad Hayisraeli]

----- 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