linux-ext4 - mount issue for ext4 filesystem with hibernation support.

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 for Android: free password hash cracker in your pocket

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

Date:   Thu, 18 Jan 2018 12:38:08 +0530
From:   "Amit Agarwal" <amit.a@...hpartnertech.com>
To:     <linux-ext4@...r.kernel.org>
Subject: mount issue for ext4 filesystem with hibernation support.

Hello

When we added the hibernation support for android M, we are able to
hibernate and resume properly.but I want to resume every time from single
snapshot image which have been taken at first-boot. 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 as 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)?

Regards,
Amit Agarwal

-- 

This message contains confidential information and is intended only for the 
individual(s) named. If you are not the intended recipient, you are 
notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this mail and attached file/s is strictly 
prohibited. Please notify the sender immediately and delete this e-mail 
from your system. E-mail transmission cannot be guaranteed to be secured or 
error-free as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses. The sender therefore does 
not accept liability for any errors or omissions in the contents of this 
message, which arise as a result of e-mail transmission.