Re: [Yaffs] yaffs can not be mounted

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Charles Manning
Date:  
To: michael.wu
CC: charles, yaffs
Subject: Re: [Yaffs] yaffs can not be mounted
Hello

On Friday 13 August 2010 19:59:36 michael.wu wrote:
> Hi maning,
>
> I use yaffs2 filesystem on linux(kernel version is 2.6.21). We test power
> failures and runs for about one week, then one partition can not be mounted
> and error message as follows:
>
> Partially written block 4617 detected

...
> Partially written block 4617 detected


That is nothing to worry about. This is just an info message.

>
> yaffs tragedy: Bad object type, -1 != 15, for object 267386879 at chunk
> 295505 during scan
>
> yaffs tragedy: Bad object type, 1 != 3, for object 325 at chunk 52246
> during scan


That is due to a tags corruption. If you are using old code then newer code
will handle this better.

>
> I don't know which version about the yaffs2. I download the newest yaffs2
> and put in Linux kernel, however, compile error, error message:
>
> fs/built-in.o: In function `yaffs_BackgroundThread':
>
> fs/yaffs2/yaffs_fs.c:2211: undefined reference to `set_freezable'
>
> fs/yaffs2/yaffs_fs.c:2211: relocation truncated to fit: R_MIPS_26 against
> `set_freezable'
>
> fs/yaffs2/yaffs_fs.c:2256: undefined reference to `init_timer_on_stack'
>
> fs/yaffs2/yaffs_fs.c:2256: relocation truncated to fit: R_MIPS_26 against
> `init_timer_on_stack'


What version of Linux are you using?

You can just disable background gc to make this go away for now. Otherwise
just comment out that line.

-- CHarles