All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Amit Agarwal" <amit.a@pathpartnertech.com>
To: <linux-ext4@vger.kernel.org>
Subject: mount issue for ext4 filesystem with hibernation support.
Date: Thu, 18 Jan 2018 12:38:08 +0530	[thread overview]
Message-ID: <014f01d3902b$19a3e040$4ceba0c0$@pathpartnertech.com> (raw)

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.

                 reply	other threads:[~2018-01-18  7:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='014f01d3902b$19a3e040$4ceba0c0$@pathpartnertech.com' \
    --to=amit.a@pathpartnertech.com \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.