linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matteo Croce <technoboy85@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: Massive filesystem corruption
Date: Sat, 20 Dec 2008 19:14:43 +0100	[thread overview]
Message-ID: <200812201914.43614.technoboy85@gmail.com> (raw)

Hi,
i've lost my ext4 partition with a 2.6.27 vanilla kernel:

root@ubuntu:~# mount -t ext4dev /dev/sda1 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

root@ubuntu:~# dmesg | tail -1
[ 4874.514703] VFS: Can't find ext4 filesystem on dev sda1.
root@ubuntu:~# e2fsck /dev/sda1
e2fsck 1.41.3 (12-Oct-2008)
e2fsck: Superblock invalid, trying backup blocks...
/dev/sda1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error1: Corrupt extent header on inode 107192
Aborted (core dumped)
root@ubuntu:~# gdb -q --args e2fsck /dev/sda1
(gdb) run
Starting program: /sbin/e2fsck /dev/sda1
[Thread debugging using libthread_db enabled]
e2fsck 1.41.3 (12-Oct-2008)
/sbin/e2fsck: Superblock invalid, trying backup blocks...
/dev/sda1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error1: Corrupt extent header on inode 107192
[New Thread 0xb7e46700 (LWP 12878)]

Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb7e46700 (LWP 12878)]
0xb8031430 in __kernel_vsyscall ()
(gdb) backtrace
#0  0xb8031430 in __kernel_vsyscall ()
#1  0xb7e8c880 in raise () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7e8e248 in abort () from /lib/tls/i686/cmov/libc.so.6
#3  0x0805397b in scan_extent_node (ctx=0x9193038, pctx=0xbf830d7c, 
pb=0xbf830c5c, start_block=0, ehandle=0x91b8170) at 
/build/buildd/e2fsprogs-1.41.3/e2fsck/pass1.c:1700
#4  0x08054c02 in check_blocks (ctx=0x9193038, pctx=0xbf830d7c, 
block_buf=0x91acff0 "\225\"\005") at 
/build/buildd/e2fsprogs-1.41.3/e2fsck/pass1.c:1773
#5  0x080565ca in e2fsck_pass1 (ctx=0x9193038) at 
/build/buildd/e2fsprogs-1.41.3/e2fsck/pass1.c:1030
#6  0x08050063 in e2fsck_run (ctx=0x9193038) at 
/build/buildd/e2fsprogs-1.41.3/e2fsck/e2fsck.c:215
#7  0x0804e4b8 in main (argc=Cannot access memory at address 0x324e
) at /build/buildd/e2fsprogs-1.41.3/e2fsck/unix.c:1278
(gdb)

please if you know how can I read, fix or debug it answer in a reasonable time,
i need that disk space and i'll format it in a few days

         reply	other threads:[~2008-12-20 18:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-23  5:49 (resend) extent header problems following shrink with resize2fs Paul Collins
2008-12-23  6:18 ` Theodore Tso
2008-12-20 18:14   ` Matteo Croce [this message]
2008-12-20 19:27     ` Massive filesystem corruption Eric Sandeen
2008-12-21  2:05       ` Matteo Croce
2008-12-21  3:23         ` Eric Sandeen
2008-12-21  5:09         ` Nick Dokos
2008-12-26  3:57         ` Theodore Tso
2008-12-25  7:18   ` (resend) extent header problems following shrink with resize2fs Paul Collins
2008-12-25 13:09     ` Theodore Tso
2008-12-26  4:14     ` 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=200812201914.43614.technoboy85@gmail.com \
    --to=technoboy85@gmail.com \
    --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).