Re: jffs2 BUG() in gc.c:135 "Checked all inodes but still..."

[Victor Tse <victortse@avantwave.com>]

Hi,

I updated to the latest code and rebuilt the filesystem by eraseall,
mount then copy the files into it. There is no problem if I umount it
before reboot, but the BUG() appears if I did not umount it.

This log is taken after copying the files, umount and then reboot:
http://www.avantwave.com/~victortse/jffs2.log1.gz

Then reboot withing umounting:
http://www.avantwave.com/~victortse/jffs2.log2.gz

Many thanks.

Regards,
Victor Tse

On Thu, 2002-09-19 at 18:59, David Woodhouse wrote:
> victortse@avantwave.com said:
> >  Before updating to the latest code there had been strange behaviors
> > e.g. seemingly corrupted executable files that restores itself after a
> > reboot, and we get different bad CRC reports every time the system
> > boots up. However generally the system is stable enough for our
> > development.
> 
> Can you provide more details? These aren't expected, except the CRC errors, 
> which shouldn't be common -- they should only happen on power loss.
> 
> > Is the new code compatible with old data? Should I just rebuild the
> > whole filesystem with the new code by erasing it and copying all files
> > into it? Any help is greatly appreciated... 
> 
> Yes, the new code is compatible. September 6th was a bad time to take a 
> snapshot -- can you update and try again?
> 
> If you can reproduce it still, please provide a full log of the mount with 
> CONFIG_JFFS2_FS_DEBUG=1.
> 
> 
> --
> dwmw2
-- 
Victor Tse <victortse@avantwave.com>