linux-ext4 - Re: Recovering a damaged ext4 fs

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <498BB63D.50503@redhat.com>
Date:	Thu, 05 Feb 2009 22:02:05 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	"J.D. Bakker" <jdb@...tmaker.nl>
CC:	linux-ext4@...r.kernel.org
Subject: Re: Recovering a damaged ext4 fs - revisited.

J.D. Bakker wrote:
> Hi,
> 
> My 4TB ext4 RAID-6 has just become damaged for the second time in two 
> months. While I do have backups for most of my data, it would be good 
> to know if there is a recovery procedure or a way to avoid these 
> crashes. The symptoms are massive group descriptor corruption, 
> similar to what was mentioned in 
> http://thread.gmane.org/gmane.comp.file-systems.ext4/10844 and 
> http://article.gmane.org/gmane.comp.file-systems.ext4/11195 .

.... snip ....

>    Error writing block 1 (Attempt to write block from filesystem 
> resulted in short write).  Ignore error? no
>    Error writing block 2 (Attempt to write block from filesystem 
> resulted in short write).  Ignore error? no
>    Error writing block 3 (Attempt to write block from filesystem 
> resulted in short write).  Ignore error? no
>    [...]
>    Error writing block 231 (Attempt to write block from filesystem 
> resulted in short write).  Ignore error? no
>    Error writing block 232 (Attempt to write block from filesystem 
> resulted in short write).  Ignore error? no
> 
> (full log at http://lartmaker.nl/ext4/e2fsck-md0.txt)

Those seem a bit odd; why are these write failing?  Anything in the
kernel logs when this happens?  I'm just wondering if there could be
some underlying storage problem?

Thanks,
-Eric
--
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