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

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

Date:	Mon, 28 Mar 2016 16:05:17 +0100 (GMT+01:00)
From:	luvar@...intext.sk
To:	linux-ext4@...r.kernel.org
Subject: corrupted fs, one nonreadable file after fsck

Hi here, I have trouble with one lost file. fsck does not print any problem, but cat on file will print "No such device or address". diff prints something like "is a block special file while file".

Background:
I have raid10 (layout -n3) on mdraid. On top of that some lvm and in one volume I have ext4 fs. I have had some problems with out of sync mdraid, which I have fixed, so I do not know why fsck found a while ago some problems. They are all now "fixed" and fsck -fFn founds nothing.

fsck.ext4 -V
e2fsck 1.42.9 (4-Feb-2014)
        Using EXT2FS Library version 1.42.9, 4-Feb-2014

Thanks for info,
LuVar
--
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