linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "J.D. Bakker" <jdb@lartmaker.nl>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Recovering a damaged ext4 fs - revisited.
Date: Thu, 05 Feb 2009 22:02:05 -0600	[thread overview]
Message-ID: <498BB63D.50503@redhat.com> (raw)
In-Reply-To: <p06240517c5b14e12f7d1@[10.1.5.33]>

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

  reply	other threads:[~2009-02-06  4:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06  3:06 Recovering a damaged ext4 fs - revisited J.D. Bakker
2009-02-06  4:02 ` Eric Sandeen [this message]
2009-02-06 12:18   ` J.D. Bakker
2009-02-06 15:23     ` Eric Sandeen
2009-02-06  6:29 ` Andreas Dilger
2009-02-06 12:23   ` J.D. Bakker
2009-02-06 21:44     ` Andreas Dilger
2009-02-06 22:15 ` Ric Wheeler
2009-02-06 22:34   ` J.D. Bakker
2009-02-06 22:43     ` Ric Wheeler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=498BB63D.50503@redhat.com \
    --to=sandeen@redhat.com \
    --cc=jdb@lartmaker.nl \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).