All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kelly Kane <kelly@hq.newdream.net>
To: linux-ext4@vger.kernel.org
Subject: Re: Call traces on console from a test machine
Date: Thu, 13 Nov 2008 18:16:48 -0800	[thread overview]
Message-ID: <491CDF90.8070802@hq.newdream.net> (raw)
In-Reply-To: <491CC6E3.7070808@hq.newdream.net>

Kelly Kane wrote:
> 
> This is a vanilla 2.6.27 kernel + grsec + "2.6.27-ext4-2" patchset + the 
> following patch per Sandeen:
> 
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=3c37fc86d20fe35be656f070997d62f75c2e4874;hp=8c9fa93d51123c5540762b1a9e1919d6f9c4af7c 
> 

I applied patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=8c3f25d8950c3e9fe6c9849f88679b3f2a071550#patch1

and built a new kernel.

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?


Also, to append my prior email, this is the original error from the machine:

Nov 13 15:58:49 watanabe EXT4-fs error (device sdb1): 
htree_dirblock_to_tree: bad entry in directory #51577: rec_len % 4 != 0 
- offset=0, inode=943022112, rec_len=13614, name_len=52
Nov 13 15:58:49 watanabe Aborting journal on device sdb1:8.
Nov 13 15:58:49 watanabe Remounting filesystem read-only


Kelly


  reply	other threads:[~2008-11-14  2:17 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 [this message]
2008-11-14 10:36   ` Andreas Dilger
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=491CDF90.8070802@hq.newdream.net \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.