From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konstantin Dorfman Subject: ext4: Aborting journal on device Date: Tue, 14 Jan 2014 18:07:10 +0200 Message-ID: <52D560AE.5010103@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: "linux-fsdevel@vger.kernel.org" , Theodore Ts'o Return-path: Received: from smtp.codeaurora.org ([198.145.11.231]:51951 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751664AbaANQHQ (ORCPT ); Tue, 14 Jan 2014 11:07:16 -0500 Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hello all, Please help me with root cause of [subj] error. I have following setup: 1. kernel 3.4 (probably some fixes are absent). 2. Read/write ext4 partition mounted with: nosuid,nodev,barrier=1,noauto_da_alloc 3. Partition located on eMMC device. 4. This is Android board. Error occurs, while doing simple reboot loop: 1. echo u > /proc/sysrq-trigger 2. poll for all /proc/mount is read only 3. power cycle. 4. goto 1 kernel log: [--cut--] [ 21.784023] EXT4-fs error (device mmcblk0p24): ext4_lookup:1044: inode #236185: comm er.ServerThread: deleted inode referenced: 236585 <3>[ 21.795347] Aborting journal on device mmcblk0p24-8. <2>[ 21.800870] EXT4-fs (mmcblk0p24): Remounting filesystem read-only <2>[ 21.807065] EXT4-fs error (device mmcblk0p24): ext4_lookup:1044: inode #236185: comm er.ServerThread: deleted inode referenced: 236585 <2>[ 22.391986] EXT4-fs error (device mmcblk0p24): ext4_lookup:1044: inode #236204: comm Error dump: sys: deleted inode referenced: 236586 <2>[ 22.409420] EXT4-fs error (device mmcblk0p24): ext4_lookup:1044: inode #236204: comm Error dump: sys: deleted inode referenced: 236587 <2>[ 22.423569] EXT4-fs error (device mmcblk0p24): ext4_lookup:1044: inode #236204: comm Error dump: sys: deleted inode referenced: 236588 <6>[ 22.446258] calling msm_rng_bus_scale(LOW) <2>[ 22.449991] EXT4-fs error (device mmcblk0p24): ext4_lookup:1044: inode #236204: comm Error dump: sys: deleted inode referenced: 236589 <2>[ 22.466499] EXT4-fs error (device mmcblk0p24): ext4_lookup:1044: inode #236204: comm Error dump: sys: deleted inode referenced: 236590 <2>[ 22.484209] EXT4-fs error (device mmcblk0p24): ext4_lookup:1044: inode #236204: comm Error dump: sys: deleted inode referenced: 236591 [--cut--] On next boot e2fsck checker output looks like this: [--cut--] <4>[ 5.818606] EXT4-fs warning (device mmcblk0p24): ext4_clear_journal_err:4100: Filesystem error recorded from previous mount: IO failure <4>[ 5.821330] ueventd used greatest stack depth: 5940 bytes left <3>[ 5.821655] firmware 5-0020: firmware_loading_store: unexpected value (0) <3>[ 5.822283] synaptics_rmi4_i2c 5-0020: fwu_start_reflash: Firmware image PR1468813.img not available <4>[ 5.851485] EXT4-fs warning (device mmcblk0p24): ext4_clear_journal_err:4101: Marking fs in need of filesystem check. <4>[ 5.863797] EXT4-fs (mmcblk0p24): warning: mounting fs with errors, running e2fsck is recommended <6>[ 5.872143] EXT4-fs (mmcblk0p24): recovery complete <6>[ 5.877334] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro <7>[ 5.887116] SELinux: initialized (dev mmcblk0p24, type ext4), uses xattr <6>[ 5.950596] fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/userdata, reason mount() return 0 <4>[ 6.487123] e2fsck used greatest stack depth: 5408 bytes left <6>[ 6.491894] e2fsck: e2fsck 1.41.14 (22-Dec-2010) <6>[ 6.496502] e2fsck: /dev/block/platform/msm_sdcc.1/by-name/userdata contains a file system with errors, check forced. <6>[ 6.507049] e2fsck: Pass 1: Checking inodes, blocks, and sizes <6>[ 6.512839] e2fsck: Pass 2: Checking directory structure <6>[ 6.518165] e2fsck: Entry 'auth_recovery_state.xml' in /data/com.google.android.gms/shared_prefs (146989) has deleted/unused inode 147261. Clear? yes <6>[ 6.531606] e2fsck: <6>[ 6.533777] e2fsck: Entry 'appwidgets.xml' in /system/users/0 (236185) has deleted/unused inode 236585. Clear? yes <6>[ 6.544195] e2fsck: <6>[ 6.546346] e2fsck: Entry 'system_app_wtf@86415310.txt' in /system/dropbox (236204) has deleted/unused inode 236586. Clear? yes <6>[ 6.557921] e2fsck: <6>[ 6.560063] e2fsck: Entry 'system_app_wtf@86415311.txt' in /system/dropbox (236204) has deleted/unused inode 236587. Clear? yes <6>[ 6.571633] e2fsck: <6>[ 6.573797] e2fsck: Entry 'system_app_wtf@86415312.txt' in /system/dropbox (236204) has deleted/unused inode 236588. Clear? yes <6>[ 6.585338] e2fsck: <6>[ 6.587492] e2fsck: Entry 'system_app_wtf@86415313.txt' in /system/dropbox (236204) has deleted/unused inode 236589. Clear? yes <6>[ 6.599053] e2fsck: <6>[ 6.601208] e2fsck: Entry 'system_app_strictmode@86415314.txt.gz' in /system/dropbox (236204) has deleted/unused inode 236590. Clear? yes <6>[ 6.613646] e2fsck: <6>[ 6.615792] e2fsck: Entry 'system_app_strictmode@86422646.txt.gz' in /system/dropbox (236204) has deleted/unused inode 236591. Clear? yes <6>[ 6.628223] e2fsck: <6>[ 6.630373] e2fsck: Pass 3: Checking directory connectivity <6>[ 6.635948] e2fsck: Pass 4: Checking reference counts <6>[ 6.640963] e2fsck: Unattached inode 147017 <6>[ 6.645147] e2fsck: Connect to /lost+found? yes <6>[ 6.649642] e2fsck: <6>[ 6.651814] e2fsck: Inode 147017 ref count is 2, should be 1. Fix? yes <6>[ 6.658429] e2fsck: <6>[ 6.660582] e2fsck: Unattached inode 147222 <6>[ 6.664774] e2fsck: Connect to /lost+found? yes <6>[ 6.669260] e2fsck: <6>[ 6.671432] e2fsck: Inode 147222 ref count is 2, should be 1. Fix? yes <6>[ 6.678048] e2fsck: <6>[ 6.680199] e2fsck: Pass 5: Checking group summary information <6>[ 6.686036] e2fsck: Block bitmap differences: +84498 -590688 -(951912--951916) +968200 +968220 -972313 -972320 -(972324--972325) -975369 +975380 -975381 -975390 <6>[ 6.700444] e2fsck: Fix? yes <6>[ 6.703289] e2fsck: <6>[ 6.705478] e2fsck: Free blocks count wrong for group #2 (14702, counted=14701). <6>[ 6.712837] e2fsck: Fix? yes <6>[ 6.715727] e2fsck: <6>[ 6.717873] e2fsck: Free blocks count wrong for group #18 (31897, counted=31898). <6>[ 6.725357] e2fsck: Fix? yes <6>[ 6.728202] e2fsck: <6>[ 6.730373] e2fsck: Free blocks count wrong for group #29 (31805, counted=31814). <6>[ 6.737856] e2fsck: Fix? yes <6>[ 6.740701] e2fsck: <6>[ 6.742872] e2fsck: Free blocks count wrong (1138114, counted=1138123). <6>[ 6.749488] e2fsck: Fix? yes <6>[ 6.752333] e2fsck: <6>[ 6.754524] e2fsck: Inode bitmap differences: +147017 -147261 -(236585--236591) <6>[ 6.761883] e2fsck: Fix? yes <6>[ 6.764772] e2fsck: <6>[ 6.766918] e2fsck: Free inodes count wrong for group #29 (7729, counted=7736). <6>[ 6.774228] e2fsck: Fix? yes <6>[ 6.777073] e2fsck: <6>[ 6.779244] e2fsck: Free inodes count wrong (307789, counted=307796). <6>[ 6.785685] e2fsck: Fix? yes <6>[ 6.788532] e2fsck: <6>[ 6.790702] e2fsck: <6>[ 6.792873] e2fsck: /dev/block/platform/msm_sdcc.1/by-name/userdata: ***** FILE SYSTEM WAS MODIFIED ***** <6>[ 6.802442] e2fsck: /dev/block/platform/msm_sdcc.1/by-name/userdata: 1676/309472 files (6.5% non-contiguous), 98865/1236988 blocks <6>[ 6.814169] e2fsck: e2fsck terminated by exit(1) [--cut--] -- sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation