linux-ext4 - Re: EXT4-fs error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 13 Mar 2012 08:14:12 -0400
From:	Ted Ts'o <tytso@....edu>
To:	manikanta <manikanta4u@...il.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: EXT4-fs error

On Tue, Mar 13, 2012 at 03:09:07PM +0530, manikanta wrote:
> Hi,
> 
> Below are the error logs,
> <2>[ 4236.400030] [0:     Thread-980:11795] EXT4-fs error (device
> mmcblk0p17): ext4_map_blocks:1304: inode #2: block 3900: comm
> Thread-980: lblock 0 mapped to illegal pblock (length 1)

You have a corrupted file system.  You need to run e2fsck on it (or
reformat it if there's nothing else that you care about on that
partition).

Block 3900 is probably (I'd need to look at the output of dumpe2fs to
be sure) overlapping with the inode table, or some other file system
metadata, and the system is refusing to write to the file system lest
more data be lost.

Regards,

					- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html