linux-ext4 - [Bug 198505] New: Errors from EXt4 FS when resuming from single hibernation image

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-198505-13602@https.bugzilla.kernel.org/>
Date:   Thu, 18 Jan 2018 11:12:47 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...nel.org
Subject: [Bug 198505] New: Errors from EXt4 FS when resuming from single
 hibernation image

https://bugzilla.kernel.org/show_bug.cgi?id=198505

            Bug ID: 198505
           Summary: Errors from EXt4 FS when resuming from single
                    hibernation image
           Product: File System
           Version: 2.5
    Kernel Version: kernel-3.18.49
          Hardware: ARM
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@...nel-bugs.osdl.org
          Reporter: omkar062@...il.com
        Regression: No

I am trying to optimize boot time in Android M, using hibernation method.
Finally I am able to do hibernate and resume properly, but for every boot I
should take snapshot image of RAM and have to resume from that image. Here my
requirement is I want to resume every time from single snapshot image. But i am
having problem with that image after 2nd boot onwards.

I am getting ext4 error, seems like block number mismatch and that file-system
on that partition is being remounted into read-only mode.

Below errors i am getting every time after 2nd boot onwards:

[   64.250735] EXT4-fs error (device mmcblk0p24): ext4_mb_generate_buddy:758:
group 9, block bitmap and bg descriptor inconsistent: 31166 vs 31165 free
clusters
[   64.252813] <3> (3)[1507:PackageManager]Aborting journal on device
mmcblk0p24-8.
[   64.267680] <3> (3)[1507:PackageManager]EXT4-fs (mmcblk0p24): Remounting
filesystem read-only
[   64.268667] <3> (1)[1:init]init: Starting service 'media'...
[   64.269479] <3> (3)[1507:PackageManager]EXT4-fs error (device mmcblk0p24) in
ext4_free_blocks:4881: Journal has aborted
[   64.272235] <3> (3)[1507:PackageManager]EXT4-fs error (device mmcblk0p24) in
ext4_reserve_inode_write:4999: Journal has aborted
[   64.278537] <3> (3)[1507:PackageManager]EXT4-fs error (device mmcblk0p24) in
ext4_reserve_inode_write:4999: Journal has aborted
[   64.283132] <3> (3)[1507:PackageManager]EXT4-fs error (device mmcblk0p24) in
ext4_ext_remove_space:3035: Journal has aborted
[   64.286970] <3> (3)[1507:PackageManager]EXT4-fs error (device mmcblk0p24) in
ext4_ext_truncate:4669: Journal has aborted
[   64.291775] <3> (3)[1507:PackageManager]EXT4-fs error (device mmcblk0p24) in
ext4_reserve_inode_write:4999: Journal has aborted
[   64.294465] <3> (3)[1507:PackageManager]EXT4-fs error (device mmcblk0p24) in
ext4_truncate:3894: Journal has aborted
[   64.297764] <3> (3)[1507:PackageManager]EXT4-fs error (device mmcblk0p24) in
ext4_reserve_inode_write:4999: Journal has aborted
[   64.300437] <3> (3)[1507:PackageManager]EXT4-fs error (device mmcblk0p24) in
ext4_orphan_del:2888: Journal has aborted

This is happening because mounted partition meta-data in RAM(old snapshot
image) is not matched with actual data in disk.

Please suggest me some way to overcome this problem.
Also is it possible to update file-system's meta-data to RAM from
partition(mounted and used by some apps)?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.