From: Angelo Dureghello <angelo70@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: ext4 errors on kernel 3.17.0
Date: Fri, 14 Nov 2014 17:52:37 +0100 [thread overview]
Message-ID: <54663355.2080903@gmail.com> (raw)
Dear all,
i am running kernel 3.17.0 (migrating from 3.5.1) on an am1808 (arm)
based custom board, with a microsd card formatted ext4.
Strangely, starting from a new formatted ext4 partition (mkfs.ext4)
after some files are written from a running application, i getseveral
errors trying fsck.ext4 or trying to remove the files manually (rm):
[root@barix media]# fsck.ext4 /dev/mmcblk0p1
e2fsck 1.42.4 (12-June-2012)
ext2fs_check_desc: Corrupt group descriptor: bad block for block bitmap
fsck.ext4: Group descriptors look bad... trying backup blocks...
/dev/mmcblk0p1 was not cleanly unmounted, check forced.
Resize inode not valid. Recreate<y>? Automount: /dev/mmcblk0p1 inserted
Automount: DEVICE LOCK found quiting...
[root@barix mmcsd0p1]# rm -r soundscape/
EXT4-fs error (device mmcblk0p1): ext4_lookup:1441: inode #260611: comm
rm: 'streams' linked to parent dir
rm: can't stat 'EXT4-fs warning (device mmcblk0p1): empty_dir:2520: bad
directory (dir #260611) - no `.' or `..'
soundscape/set_1/configuration/streams/streams': Input/output error
EXT4-fs warning (device mmcblk0p1): empty_dir:2520: bad directory (dir
#260618) - no `.' or `..'
EXT4-fs warning (device mmcblk0p1): empty_dir:2520: bad directory (dir
#260615) - no `.' or `..'
EXT4-fs warning (device mmcblk0p1): empty_dir:2520: bad directory (dir
#260616) - no `.' or `..'
EXT4-fs error (device mmcblk0p1): ext4_lookup:1448: inode #260617: comm
rm: deleted inode referenced: 260611
rm: can't stat 'EXT4-fs warning (device mmcblk0p1): empty_dir:2520: bad
directory (dir #260617) - no `.' or `..'
soundscape/set_1/firmware/streams': Input/output error
EXT4-fs error (device mmcblk0p1): ext4_lookup:1448: inode #260619: comm
rm: deleted inode referenced: 260611
rm: can't stat 'EXT4-fs warning (device mmcblk0p1): empty_dir:2520: bad
directory (dir #260619) - no `.' or `..'
soundscape/set_1/schedule/streams': Input/output error
EXT4-fs error (device mmcblk0p1): ext4_lookup:1448: inode #260610: comm
rm: deleted inode referenced: 260611
rm: can't stat 'soundscape/downloads/streams': Input/output error
rm: can't remove 'soundscape/downloads': Directory not empty
rm: can't remove 'soundscape': Directory not empty
[root@barix mmcsd0p1]#
I cannot reproduce these errors on kernel 3.5.1.
Every help is very appreciated.
Angelo
next reply other threads:[~2014-11-14 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 16:52 Angelo Dureghello [this message]
2014-11-19 13:09 ` ext4 errors on kernel 3.17.0 Angelo Dureghello
2014-11-19 13:50 ` Theodore Ts'o
2014-11-20 11:16 ` Angelo Dureghello
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=54663355.2080903@gmail.com \
--to=angelo70@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).