linux-ext4 - Re: ext4 errors not going away after fsck

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

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

Date:	Thu, 25 Nov 2010 12:09:17 -0700
From:	Andreas Dilger <adilger@...ger.ca>
To:	Tomasz Chmielewski <mangoo@...g.org>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: ext4 errors not going away after fsck

On 2010-11-25, at 07:57, Tomasz Chmielewski wrote:
> I have a system which had bad memory.
> 
> Bad memory was replaced, but filesystem corruption caused by it (and related crashes) is still there:
> 
> [104472.909769] EXT4-fs (vdb1): mounted filesystem with ordered data mode. Opts: errors=remount-ro
> [104773.600088] EXT4-fs (vdb1): error count: 2
> [104773.600093] EXT4-fs (vdb1): initial error at 1290468286: htree_dirblock_to_tree:586: inode 30204507: block 120625971
> [104773.600097] EXT4-fs (vdb1): last error at 1290468334: ext4_put_super:726: inode 30204507: block 120625971

The "initial error" handling has been fixed in the e2fsprogs git repo.  Search the archives for the patch.

> The error is exactly the same as the first one I pasted (multiple umount, fsck, mount runs without reboot).
> 
> Is this all something to be worry about?

No, this is just a historical log of what caused the filesystem problems.  It doesn't mean that there is anything wrong with the filesystem now.

Cheers, Andreas





--
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