[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New jffs2 files stay uncompressed?



> > jffs2_scan_empty(): Empty block at 0x0012fffc ends at 0x00130000 (with 0xe0021985)! Marking dirty
> 
> No, that just means you used the wrong eraseblock size when making the 
> image. Use the correct '-e' argument to mkfs.jffs2 and it won't complain. 
> The messages are harmless though.

What is "wrong" resp. "correct" in this context?  Compared to what?
I used no -e, so the default size should be 64 KB, according to the
help text, and I also compiled the blkmtd driver with the same
erase size.

-- 
--    Jos Vos <jos@xxxxxxx.nl>
--    X/OS Experts in Open Systems BV   |   Phone: +31 20 6938364
--    Amsterdam, The Netherlands        |     Fax: +31 20 6948204

To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo@xxxxxxx.com