linux-ext4 - 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 30 Sep 2014 19:56:36 +0200
From:	Zlatko Calusic <zcalusic@...sync.net>
To:	linux-ext4@...r.kernel.org
Subject: e2fsck not fixing deleted inode referenced errors?

Hope this is the right list to ask this question.

I have an ext4 filesystem that has a few errors like this:

Sep 30 19:14:09 atlas kernel: EXT4-fs error (device md2): 
ext4_lookup:1448: inode #7913865: comm find: deleted inode referenced: 
7912058
Sep 30 19:14:09 atlas kernel: EXT4-fs error (device md2): 
ext4_lookup:1448: inode #7913865: comm find: deleted inode referenced: 
7912055

Yet, when I run e2fsck -fy on it, I have a clean run, no errors are 
found and/or fixed. Is this the expected behaviour? What am I supposed 
to do to get rid of errors like the above?

The filesystem is on a md mirror device, the kernel is 3.17.0-rc7, 
e2progs 1.42.12-1 (Debian sid). Could md device somehow interfere? I ran 
md check yesterday, but there were no errors.

BTW, this all started when I got ata2.00: failed command: FLUSH CACHE 
EXT error yesterday morning. I did several runs of e2fsck before the 
filesystem came up clean, yet errors like the above are popping constantly.

Thanks for any info. [and please Cc:, I'm not subscribed]

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