UBIFS assert when rebooting a read only ubifs when it's been remounted r/w

[Richard Weinberger]

Am 20.05.2016 um 09:49 schrieb Richard Weinberger:
> Am 18.05.2016 um 12:39 schrieb Martin Townsend:
>> I can't do the sync as the error only occurs during boot and I can see
>> the assert whilst systemd is rmounting all the filesystems. Once I've
>> logged in I can't get the assert to trigger again.  Just to summarise
>> the conditions for triggering the assert
>> To trigger I login and remount / as rw and then reboot (to a ro
>> rootfs) and the assert first during the boot.
>> The assert will appear on all subsequent boots (Providing I don't do
>> the following)
>> To get rid of the assert I can, once logged in, remount / rw and then
>> ro and then reboot.
> 
> Hmm, so there is no reset/power cut involved at all?
> Can you trigger it when you mount a UBIFS by hand ro and remount?

Another thought, can you try this patch (if it is not already applied)?

commit 807612db2f9940b9fa6deaef054eb16d51bd3e00
Author: Andrew Ruder <andrew.ruder at elecsyscorp.com>
Date:   Thu Jan 30 09:26:54 2014 -0600

    fs/super.c: sync ro remount after blocking writers

    Move sync_filesystem() after sb_prepare_remount_readonly().  If writers
    sneak in anywhere from sync_filesystem() to sb_prepare_remount_readonly()
    it can cause inodes to be dirtied and writeback to occur well after
    sys_mount() has completely successfully.

    This was spotted by corrupted ubifs filesystems on reboot, but appears
    that it can cause issues with any filesystem using writeback.

    Cc: Artem Bityutskiy <dedekind1 at gmail.com>
    Cc: Christoph Hellwig <hch at infradead.org>
    Cc: Alexander Viro <viro at zeniv.linux.org.uk>
    CC: Richard Weinberger <richard at nod.at>
    Co-authored-by: Richard Weinberger <richard at nod.at>
    Signed-off-by: Andrew Ruder <andrew.ruder at elecsyscorp.com>
    Signed-off-by: Al Viro <viro at zeniv.linux.org.uk>

Thanks,
//richard