From: Theodore Ts'o <tytso@mit.edu>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4_free_inode:319: comm krunner: bit already cleared for inode 6293718
Date: Thu, 3 Jan 2013 13:22:35 -0500 [thread overview]
Message-ID: <20130103182235.GA5941@thunk.org> (raw)
In-Reply-To: <50E5C4C5.9040701@gmx.de>
On Thu, Jan 03, 2013 at 06:49:57PM +0100, Toralf Förster wrote:
> For the following 3 errors I think the last 2 are related to the fact,
> that I'm booting a Gentoo Linux (kernel 3.7.1) from an external USB 2.0 drive,
> but the first error, is that related too to the external drive itslef ? :
>
> 2013-01-03T16:28:04.305+01:00 n22 kernel: EXT4-fs error (device sdb3): ext4_free_inode:319: comm krunner: bit already cleared for inode 6293718
> 2013-01-03T16:28:07.426+01:00 n22 kernel: EXT4-fs error (device sdb3) in ext4_new_inode:942: IO failure
> 2013-01-03T16:28:10.683+01:00 n22 kernel: EXT4-fs error (device sdb3) in ext4_new_inode:942: IO failure
Well, what the error message means is that the kernel has detected an
inconsistency in the inode allocation bitmap.
Could this be called by an error to the external drive? Certainly.
It could also be caused by the drive getting pulled before it was
cleanly unmounted at some point in the past, and (especially if this
drive was using flash) the inode allocation bitmap got corrupted.
-- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-01-03 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 17:49 ext4_free_inode:319: comm krunner: bit already cleared for inode 6293718 Toralf Förster
2013-01-03 18:22 ` Theodore Ts'o [this message]
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=20130103182235.GA5941@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/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).