[OpenWrt-Devel] jffs takes about 18 minutes to get ready on 3.10 kernel

Claudio Thomas ct at xmodus-systems.de
Wed Oct 29 18:32:20 EDT 2014


On 29.10.2014 13:37, Bastian Bittorf wrote:
> * Claudio Thomas <ct at xmodus-systems.de> [29.10.2014 13:18]:
>> [  800.742671] jffs2: notice: (888) jffs2_build_xattr_subsystem:
> how large is the partitionsize?
"rootfs_data" created automatically, ofs=0x960000, len=0x3260000
> while we are at it:
> till r40402 we where probing jffs2_ready() before
> writing to disc (e.g. new config-files).
>
> what is the supposed way the handle that now?
> (we grep the syslog for 'complete building xattr subsystem')
Sorry for the long delay, the tests need some time :-(

I've made now a git pull+make clean, so that I've tested now again with
BB at 43085:
(For the tests I've booted using tftp+ramdisk)
1. boot 3.10 with a working jffs and 3.8 config files: ~1183s(1),
~1232s(2),
    than run "/sbin/jffs2reset -y" (323s remove files time) and
2. boot 3.10 with a empty jffs: ~1161s(1), ~1212s(2),
    than run "umount /overlay; /sbin/jffs2reset -y" (612s erase time) and
3. boot 3.10 with an erased jffs,
    see "No jffs marker found" (!) and
    received no "switching to overlay" (!) message,
    but /overlay is mounted: ~896s(1 - until complete building...), ~899s(2)
4. boot 3.10 with rebuilded jffs: ~1167(1), ~1205(2)

For comparison a 3.8 build based on CC at 43032
1. boot 3.8: ~17.2s(1);  "/sbin/jffs2reset -y" (1s remove files time)
2. boot 3.8 with empty jffs: ~5s(1); "umount /overlay; /sbin/jffs2reset
-y" (87s erase time)
3. boot 3.8 with erased jffs: ~200s(1)
4. boot 3.8 with rebuild jffs: ~17s(1)

Is this helpful or should I test anything else?
After comparing both there seem to be a performance issue, because when
looking only ate the erase time the 3.8 version erases the flash 8 times
faster. Any idea what I could check?

BTW: When booting BB at 43085 and after executing "umount /overlay;
/sbin/jffs2reset -y" I was missing the "deadc0de"? (No jffs marker found)
  # echo $(hexdump /dev/mtd1 -n 4 -e '4/1 "%02x"')
  ffffffff
To avoid this I've run
  # echo -e "\xde\xad\xc0\xde" | mtd write - mtd1
Why isn't jffs2reset marking the partition after reset? (same issue
after running /sbin/jffs2mark)

Thanks,
Claudio
-- 
Working on OpenWrt BB for Xmodus Systems XM1700E
<http://www.xmodus-systems.de/en/terminals/routers.html>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20141029/fd49b40b/attachment.htm>
-------------- next part --------------
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


More information about the openwrt-devel mailing list