linux-ext4 - Re: e2fsck not fixing deleted inode referenced errors?

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]

Message-ID: <542BA2B0.4040604@bitsync.net>
Date:	Wed, 01 Oct 2014 08:44:00 +0200
From:	Zlatko Calusic <zcalusic@...sync.net>
To:	Theodore Ts'o <tytso@....edu>
CC:	"Darrick J. Wong" <darrick.wong@...cle.com>,
	linux-ext4@...r.kernel.org
Subject: Re: e2fsck not fixing deleted inode referenced errors?

On 30.09.2014 22:27, Zlatko Calusic wrote:
>
> Unless you have other ideas, I will run badblocks. Although, as ext4 fs
> is on /dev/md2, I think I should run it on /dev/md2 only? Do you really
> mean to run it on /dev/sda2, /dev/sdb2 - underlying devices? I'm not
> sure how MD would cope with it.
>
> But, I'm pretty sure that it will come out clean. The md check I did
> last night would surely detected bad blocks if there were any. Or not?

So, I ran badblocks on both underlying devices, and both came up clean, 
as I suspected would happen. Then I ran debugfs -w /dev/md2 and unlinked 
7 inodes that were problematic. Afterwards e2fsck found those inodes and 
connected them to lost+found. Second e2fsck run finished clean. And at 
this time I see no errors on the fs.

This is definitely the case where e2fsck can't see or repair fs errors 
that are real.

Regards,
-- 
Zlatko

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