ext4_free_inode:319: comm krunner: bit already cleared for inode 6293718

ext4_free_inode:319: comm krunner: bit already cleared for inode 6293718

[Toralf Förster]

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


-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
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

Re: ext4_free_inode:319: comm krunner: bit already cleared for inode 6293718

[Theodore Ts'o]

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