<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 29.10.2014 13:37, Bastian Bittorf
wrote:<br>
</div>
<blockquote cite="mid:20141029123744.GS17340@medion.lan" type="cite">
<pre wrap="">* Claudio Thomas <a class="moz-txt-link-rfc2396E" href="mailto:ct@xmodus-systems.de"><ct@xmodus-systems.de></a> [29.10.2014 13:18]:
</pre>
<blockquote type="cite">
<pre wrap="">[ 800.742671] jffs2: notice: (888) jffs2_build_xattr_subsystem:
</pre>
</blockquote>
<pre wrap="">how large is the partitionsize?</pre>
</blockquote>
"rootfs_data" created automatically, ofs=0x960000, len=0x3260000<br>
<blockquote cite="mid:20141029123744.GS17340@medion.lan" type="cite">
<pre wrap="">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')
</pre>
</blockquote>
Sorry for the long delay, the tests need some time :-(<br>
<br>
I've made now a git pull+make clean, so that I've tested now again
with BB@43085:<br>
(For the tests I've booted using tftp+ramdisk)<br>
1. boot 3.10 with a working jffs and 3.8 config files: ~1183s(1),
~1232s(2), <br>
than run "/sbin/jffs2reset -y" (323s remove files time) and <br>
2. boot 3.10 with a empty jffs: ~1161s(1), ~1212s(2), <br>
than run "umount /overlay; /sbin/jffs2reset -y" (612s erase
time) and<br>
3. boot 3.10 with an erased jffs, <br>
see "No jffs marker found" (!) and <br>
received no "switching to overlay" (!) message, <br>
but /overlay is mounted: ~896s(1 - until complete building...),
~899s(2)<br>
4. boot 3.10 with rebuilded jffs: ~1167(1), ~1205(2)<br>
<br>
For comparison a 3.8 build based on CC@43032<br>
1. boot 3.8: ~17.2s(1); "/sbin/jffs2reset -y" (1s remove files
time)<br>
2. boot 3.8 with empty jffs: ~5s(1); "umount /overlay;
/sbin/jffs2reset -y" (87s erase time)<br>
3. boot 3.8 with erased jffs: ~200s(1)<br>
4. boot 3.8 with rebuild jffs: ~17s(1)<br>
<br>
Is this helpful or should I test anything else?<br>
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?<br>
<br>
BTW: When booting BB@43085 and after executing "umount /overlay;
/sbin/jffs2reset -y" I was missing the "deadc0de"? (No jffs marker
found) <br>
# echo $(hexdump /dev/mtd1 -n 4 -e '4/1 "%02x"')<br>
ffffffff<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
To avoid this I've run <br>
#
<meta http-equiv="content-type" content="text/html; charset=utf-8">
echo -e "\xde\xad\xc0\xde" | mtd write - mtd1<br>
Why isn't jffs2reset marking the partition after reset? (same issue
after running /sbin/jffs2mark)<br>
<br>
Thanks,<br>
Claudio<br>
<span class="HOEnZb"><font color="#888888">-- <br>
Working on OpenWrt BB for Xmodus Systems <a
href="http://www.xmodus-systems.de/en/terminals/routers.html"
target="_blank">XM1700E</a></font></span><br>
<br>
</body>
</html>