linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@sun.com>
To: Kelly Kane <kelly@hq.newdream.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Call traces on console from a test machine
Date: Fri, 14 Nov 2008 03:36:02 -0700	[thread overview]
Message-ID: <20081114103602.GU16005@webber.adilger.int> (raw)
In-Reply-To: <491CDF90.8070802@hq.newdream.net>

On Nov 13, 2008  18:16 -0800, Kelly Kane wrote:
> In the mean time, fsck.ext4 is not liking our filesystem.
>
> Group descriptor 353 checksum is invalid.  Fix? yes
> Pass 2: CheckingEntry 'spice-and-wolf-si-tendra-segunda-temporada' in
>
 
> /liamsito1234/cibercomics.com/wp-content/cache/supercache/www.cibercomics.com/2008/10/05 
> (2152305) references inode
>                2901322 in group 354 where _INODE_UNINIT is set.
> Entry 'spice-and-wolf-si-tendra-segunda-temporada' in
>
 
> /liamsito1234/cibercomics.com/wp-content/cache/supercache/www.cibercomics.com/2008/10/05 
> (2152305) has
>                deleted/unused inode 2901322.  Clear? yes
> /dev/sdb1: e2fsck canceled.
> e2fsck: aborted
>
> Same block group each run through, different inode.
>
> I ran e2image and produced the following file:
>
> http://ext4dev.dreamhosters.com/watanabe-home-2008-11-13-1712.e2image.bz2
>
> Unfortunately I cannot mount the filesystem right now due to:
>
> EXT4-fs: ext4_check_descriptors: Checksum for group 353 failed  
> (23397!=52411)
> EXT4-fs: group descriptors corrupted!
> mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
>        missing codepage or other error       In some cases useful info  
> is found in syslog - try
>        dmesg | tail  or so
>
> Is there any hope for recovery of any of this data?

You can run "tune2fs -O ^uninit_bg /dev/XXX" to disable the group
descriptor checksums (and, unfortunately, the fast fsck benefits),
but at least it will allow you to mount the filesystem.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.


  reply	other threads:[~2008-11-14 10:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14  0:31 Call traces on console from a test machine Kelly Kane
2008-11-14  2:16 ` Kelly Kane
2008-11-14 10:36   ` Andreas Dilger [this message]
2008-11-14 17:09   ` Theodore Tso
2008-11-14 20:29     ` Kelly Kane
2008-11-17 18:58     ` Kelly Kane
2008-11-17 20:30       ` Theodore Tso
2008-11-17 21:20         ` Eric Sandeen
2008-11-18  2:24           ` Theodore Tso

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=20081114103602.GU16005@webber.adilger.int \
    --to=adilger@sun.com \
    --cc=kelly@hq.newdream.net \
    --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).