CLEANMARKER message/warning/error ?

Hi

When I boot one of the last Portux we got, I receive this
message/warning/error (?). The kernel works fine and I can write on the flash
without errors:

...
Freeing init memory: 88K
Empty flash at 0x000295ec ends at 0x00030000
CLEANMARKER node found at 0x00030000, not first node in block (0x00020000) <- ???
eth0: Link now 100-FullDuplex
...

Best Regards

Paolo Celani

Re: CLEANMARKER message/warning/error ?

Normally you get this error message, when you generate an jffs2 image with 64K block size and have a flash with 128K (like on Portux later editions). Then you have a lot of them though.
The error message Empty flash at 0x000295ec ends at 0x30000 points to an incomplete write and should disappear after the next garbage collection. You can trigger the garbage thread to complete by cleanly umounting the relevant device.

Re: CLEANMARKER message/warning/error ?

I booted Portux, I logged in and ran several times "umount /config/ then
"mount /config". The answer is the same:

root@Portux920T:# umount /config
root@Portux920T:# mount /config
Empty flash at 0x000295ec ends at 0x00030000
CLEANMARKER node found at 0x00030000, not first node in block (0x00020000)
root@Portux920T:# umount /config
root@Portux920T:# mount /config
Empty flash at 0x000295ec ends at 0x00030000
CLEANMARKER node found at 0x00030000, not first node in block (0x00020000)
root@Portux920T:# umount /config
root@Portux920T:# mount /config
Empty flash at 0x000295ec ends at 0x00030000
CLEANMARKER node found at 0x00030000, not first node in block (0x00020000)

The fact is that I did not write/overwrite the flash where /config is.
At least, not that I know. I did write in all Portux that we bought the
Kernel that I compiled. The kernel booted in all cases without errors or
problems. I can provide the "dmesg" output if you think it can help.
As far as I can understand, it looks clean, apart from that error/warning.

Best regards

Paolo Celani

Re: CLEANMARKER message/warning/error ?

Sorry, that was a mistake on my side. Cleanly umounting a device does not trigger the garbage collection. If the garbage collection is running it only ensures, that it is completed.
In my regard this error message will be cleaned by the next garbage collection. You can try write to the MTD-Device until it is full, which may cause garbage collection to start to see if the error message is disappearing then. Usually garbage collection is started on an "as needed" basis.

Syndicate content