All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: InvTraySts <invtrasys@gmail.com>
Cc: Jan Kara <jack@suse.cz>, linux-ext4@vger.kernel.org
Subject: Re: Fwd: Need help with Data Recovery on Ext4 partitions that became corrupted on running OS
Date: Wed, 25 Sep 2013 19:59:50 -0500	[thread overview]
Message-ID: <52438706.3090706@redhat.com> (raw)
In-Reply-To: <CAOWv6b3OPaSMRvE8cG5_6Qkq-gUGheX7hccmLtO=z7wkekq8ZA@mail.gmail.com>

On 9/25/13 7:08 PM, InvTraySts wrote:
> (Going to merge these two back, because both of you are actually
> helping me, but with the two conversations being segregated like this
> it makes it hard to correlate with you both)
> The partprobe did work with getting the partition table reread.
> After that, the tune2fs sorta worked.
> root@server:~# tune2fs -f -O ^has_journal /dev/sdf1
> tune2fs 1.42.5 (29-Jul-2012)
> root@server:~# mount /dev/sdf1 /media/tmp
> root@server:~# ls -l /media/tmp/
> total 0
> 
> When I try and use the debugfs /dev/sdf1
> 
> root@server:~# debugfs /dev/sdf1
> debugfs 1.42.5 (29-Jul-2012)
> debugfs:  ls
> EXT2 directory corrupted
> debugfs:  ls /
> /: EXT2 directory corrupted

At this point you could try e2fsck on the _copy_, to see what it
can do.

Seems like something quite bad may have happened to your storage,
though, and e2fsck may not be magical for you.

-Eric


  reply	other threads:[~2013-09-26  0:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOWv6b1Jq0MAtELB_brhg_G3S2svEW8EaW9A8ciddTUdqDWFdQ@mail.gmail.com>
     [not found] ` <CAOWv6b1m8A2S3sjDsJxOrRVztch6iq4zH9eFq5DKFMqtWWWpEw@mail.gmail.com>
2013-09-25  2:25   ` Fwd: Need help with Data Recovery on Ext4 partitions that became corrupted on running OS InvTraySts
2013-09-25 15:35     ` Eric Sandeen
2013-09-25 16:35       ` InvTraySts
2013-09-25 16:50         ` Eric Sandeen
2013-09-25 17:09           ` InvTraySts
2013-09-25 21:45             ` Eric Sandeen
2013-09-25 23:57               ` InvTraySts
2013-09-26  0:57                 ` Eric Sandeen
2013-09-25 16:12     ` Jan Kara
2013-09-25 19:24       ` InvTraySts
2013-09-25 21:28         ` Jan Kara
2013-09-26  0:08           ` InvTraySts
2013-09-26  0:59             ` Eric Sandeen [this message]
2013-09-26  1:41               ` InvTraySts
2013-09-26  8:53             ` Jan Kara
2013-09-26 17:45               ` InvTraySts
2013-09-26 20:18                 ` Jan Kara

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=52438706.3090706@redhat.com \
    --to=sandeen@redhat.com \
    --cc=invtrasys@gmail.com \
    --cc=jack@suse.cz \
    --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.