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

Re: New jffs2 files stay uncompressed?



> The output of df isn't very reliable. But it is possible that there's a 
> problem. Do you see 'deflateInit failed' on the console? Can you check the 
> contents of the blkmtd device after you write the file, to verify that your 
> new data really aren't compressed?

Strange... it now works fine.  I'm sure it didn't work before, also not
with big, well-compressible ASCII file (I now copied a large RFC to it).
But now I see that copying a file of 286 KB uses 112 blocks, so this is
pretty good.

But I see on every mount about 10 of these messages:

jffs2_scan_empty(): Empty block at 0x0012fffc ends at 0x00130000 (with 0xe0021985)! Marking dirty

Maybe my fs is somewhat corrupted?

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