#16651: NAND space getting lost on RB450
--------------------------+-------------------------------------
Reporter: leonardogyn | Owner: developers
Type: defect | Status: new
Priority: high | Milestone: Barrier Breaker 14.07
Component: base system | Version: Trunk
Resolution: | Keywords: yaffs2 nand routerboard
--------------------------+-------------------------------------
Comment (by leonardogyn):
Some updates on this ticket, despite the fact that it seems no one cares
about it :(
Just downloaded r45988, compiled with basic config, netbooted and
installed with wget2nand on a RB450 board. Right after install, i had:
{{{
CHAOS CALMER (Bleeding Edge, r45988)
root@OpenWrt:/# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 61440 4132 57308 7% /
}}}
ran my usual stress disk write/delete test:
{{{
i=1; while true; do echo "run # $i"; rm -f /teste; dd if=/dev/urandom
of=/teste bs=1M count=5; rm -f /teste; df | head -2; i=$(($i + 1)); done
}}}
everything was looking fine, used/available space remains the same after
20 runs. So i stopped it, remove any left files and rebooted.
{{{
run # 1
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 61440 4132 57308 7% /
[ ... ]
run # 20
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 61440 4136 57304 7% /
^C
root@OpenWrt:/# rm /teste
root@OpenWrt:/# reboot
}}}
Right after rebooting, oh no, used space jumped from 4Mb to 47Mb :( So i
ran the test for some more runs.
{{{
root@OpenWrt:/# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 61440 47320 14120 77% /
run # 10
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 61440 47320 14120 77% /
^C
root@OpenWrt:/# rm /teste
root@OpenWrt:/# reboot
}}}
right after booting:
{{{
root@OpenWrt:/# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 61440 58268 3172 95% /
}}}
ran the test for some more runs, rebooted and that's it, i have no space
available anymore, this system is useless and the only way for recovering
it is reflashing.
{{{
root@OpenWrt:/# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 61440 61436 4 100% /
}}}
I started again, compiled again (same config file) but applying a patch to
force the yaffs partition to be mounted yaffs version and having the
inband-tags parameter. Things changed a lot.
Right after wget2nand and booting:
{{{
root@OpenWrt:/# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 59520 4276 55244 7% /
}}}
During the first test runs, used space was raising little by little but,
at some point, it stopped raising and kept stable no matter how many runs
i let the test run (it ran for more than 100 times)
{{{
run # 1
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 59520 4444 55076 7% /
run # 2
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 59520 4608 54912 8% /
run # 3
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 59520 4772 54748 8% /
run # 4
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 59520 4940 54580 8% /
run # 5
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 59520 5104 54416 9% /
run # 6
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 59520 5272 54248 9% /
run # 7
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 59520 5436 54084 9% /
run # 8
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 59520 5596 53924 9% /
run # 9
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 59520 5596 53924 9% /
run # 10
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 59520 5596 53924 9% /
}}}
rebooted and
{{{
root@OpenWrt:/# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 59520 5612 53908 9% /
}}}
ran the test for some runs:
{{{
run # 20
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 59520 5644 53876 9% /
}}}
rebooted again
{{{
root@OpenWrt:/# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 59520 5628 53892 9% /
}}}
Conclusions: r45988 still shows from the described problem. Forcing
inband-tags seems to be an interesting workaround, despite the fact that
on my tests it did not COMPLETLY solved the situation, as it seems that at
some point used space will also be lost forever. Given my test numbers, it
will take a MUCH longer time to get at that point, which really makes it
an interesting workaround by now, as it's the best i can acchieve by
myself.
--
Ticket URL: <https://dev.openwrt.org/ticket/16651#comment:14>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
