FS#4131 - 21.02.1 squashfs overlay retained rpi4

[openwrt-bot]

wulfy23:

Upgrading from 21.02.0 to 21.02.1 leads to whacky opkg state where previous packages are listed

see:
https://forum.openwrt.org/t/rpi-4-sysupgrade-21-02-1-squashfs-overlay-retained/110586?u=wulfy23
for further information

[openwrt-bot]

wulfy23:

note:

selection of keep settings or not makes no difference and user configs are retained even without keep settings...

21.02.0-rc4 > 21.02.0 (no problem)

21.02.0 > 21.02.1 (problem)
21.02.1 > 21.02.1 (problem)

21.02.1 > master@r18xxx+ (no problem)

[openwrt-bot]

mojifax:

i've noticed this in 21.02.0 > 21.02.0 also

1- factory install
2- set password
3- reboot
4- sysupgrade not retaining settings
5- reboot password i still set

https://forum.openwrt.org/t/raspberry-pi-4-usb-boot/109646/7

[CakeConnoisseur]

Duplicate of #5087

[TalalMash]

For those looking for a temporary workaround with no graceful shutdown options (not a problem with f2fs-squashfs):
Using ext4 image, add to rc.local mount -o rw,remount,noatime,async,barrier=1,commit=30,errors=continue /
And in /lib/preinit/80_mount_root:

....
do_mount_root() {
       if [ -x '/usr/sbin/fsck.ext4' ]; then
           if [ -e '/dev/<replacewithrootpart>' ]; then
               echo "Checking <replacewithrootpart>"
               /usr/sbin/fsck.ext4 -y /dev/<replacewithrootpart> >> /tmp/fsck-results
           fi
	fi
	mount_root
....

With automated power cycles over ~100 iterations journaling corruptions were the most common but no data corruption, only data loss. Tested with litesql writing to storage every 2 seconds. Platform: RPi4 with sdcard.
E: to add filesystem would switch to read-only between 10-20 iterations with default settings. Note that speeds degrades significantly with 'sync' option.

[wulfy23]

possible overlap/relationships with this issue

#9352

[CakeConnoisseur]

FYI: Just did a sysupgrade from 21.02.2 > 21.02.3 with the official squashfs image, this time "keep settings" was checked.
Could not reproduce the bug!

Was there a fix implemented?
AFAIK nothing mentioned here or in #9352.