Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#1755 - data not flushed to persistent storage on ubifs #6956

Closed
openwrt-bot opened this issue Aug 9, 2018 · 4 comments
Closed

FS#1755 - data not flushed to persistent storage on ubifs #6956

openwrt-bot opened this issue Aug 9, 2018 · 4 comments
Labels

Comments

@openwrt-bot
Copy link

russell:

Supply the following if possible:

  • Device problem occurs on

Observed on a Meraki MR24 (apm821xx), with NAND flash and ubifs overlay

  • Software versions of OpenWrt/LEDE release, packages, etc.

Seen on versions as old as 5979-gc9c2e4d78d and 6286-gf01b394266, and as recent as 7763-g9537c1a153.

  • Steps to reproduce

Sysupgrade or factory reset, allow to boot fully, wait a few minutes if desired, yank power. When device comes up again, I found /overlay/upper/etc/config/dropbear was all NULL (also /overlay/upper/etc/config/horst and /overlay/upper/etc/config/batman-adv). If I login to a shell (over serial or ssh) and either reboot or 'sync' before yanking power, the files in /overlay survive intact. It seems the data is not making it out to persistent storage without an explicit sync even after considerable time. In my case, the corrupted /etc/config/dropbear was a big problem, because remote access wasn't possible anymore (I initially had to crack the case to attach a serial console to figure out what was going wrong). It is possible to recover with a factory reset, followed by logging in and sync'ing or rebooting.

@openwrt-bot
Copy link
Author

russell:

In my case, the files that were zero'd out were all those in /overlay/upper/etc/config/ where the files pre-power-loss were identical (diff reports no changes) from the /rom versions.

@openwrt-bot
Copy link
Author

vzahradnik:

I also observed the issue on latest nightly build (commit dc9388a on master).
Router: Mikrotik RB450G
Filesystem: UBIFS on MLC NAND.

After I installed a package which modified some files and issued an reboot command, content was not damaged. However one package install caused router to reboot due to kernel panic and after the reboot the config files modified by the package were empty.

@openwrt-bot
Copy link
Author

jaimet:

I think that I have the same problem on a BT Home Hub v2B (OpenWrt 18.06.1) here:
https://bugs.openwrt.org/index.php?do=details&task_id=1842

@openwrt-bot
Copy link
Author

russell:

This is fixed for me with commit c6a1bca

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant