Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.misc > #15052

Re: Recovering an EXT3 FS - hopeless if inode list is overwritten?

From "Charles T. Smith" <cts.private.yahoo@gmail.com>
Newsgroups comp.os.linux.misc
Subject Re: Recovering an EXT3 FS - hopeless if inode list is overwritten?
Date 2015-07-14 07:55 +0000
Organization A noiseless patient Spider
Message-ID <mo2f8v$g2e$1@dont-email.me> (permalink)
References <mjmo0k$a0i$1@dont-email.me> <AABVXuscNOAAAAl7.A1.flnews@WStation3.stz-e.de> <mnto2i$cc2$1@dont-email.me> <AABVo53Dk5oAAA1l.A1.flnews@WStation3.stz-e.de> <mo17hn$kcv$1@dont-email.me>

Show all headers | View raw


A couple of notes to this superblock dump:

- the mtime/wtime values represent
  2014/11/11 12:48:56
  Definitely plausible

- the two arrays are not properly implemented by the dump program
(s_hash_seed and s_reserved).

On Mon, 13 Jul 2015 20:37:12 +0000, Charles T. Smith wrote:

>   $ sudo dd if=/dev/sdc1 bs=512 count=1 skip=206983138 |
>   ../../bin/blkdump
>      78000:       s_inodes_count;         /* Inodes count */
>     1dff00:       s_blocks_count;         /* Blocks count */
>      17ff3:       s_r_blocks_count;       /* Reserved blocks count */
>      f7099:       s_free_blocks_count;    /* Free blocks count */
>      4c3da:       s_free_inodes_count;    /* Free inodes count */
>          0:       s_first_data_block;     /* First Data Block */
>          2:       s_log_block_size;       /* Block size */
>          2:       s_log_frag_size;        /* Fragment size */
>       8000:       s_blocks_per_group;     /* # Blocks per group */
>       8000:       s_frags_per_group;      /* # Fragments per group */
>       2000:       s_inodes_per_group;     /* # Inodes per group */
>   5461f7a8:       s_mtime;                /* Mount time */
>   5461f7a8:       s_wtime;                /* Write time */
>          3:       s_mnt_count;            /* Mount count */
>       ffff:       s_max_mnt_count;        /* Maximal mount count */
>       ef53:       s_magic;                /* Magic signature */
>          1:       s_state;                /* File system state */
>          1:       s_errors;               /* Behaviour when detecting...
>          0:       s_minor_rev_level;      /* minor revision level */
>   5461e8b0:       s_lastcheck;            /* time of last check */
>          0:       s_checkinterval;        /* max. time between checks */
>          0:       s_creator_os;           /* OS */
>          1:       s_rev_level             /* Revision level */
>          0:       s_def_resuid;           /* Default uid for reserved...
>          0:       s_def_resgid;           /* Default gid for reserved...
>          b:       s_first_ino;            /* First non-reserved inode */
>        100:   s_inode_size;               /* size of inode structure */
>          0:       s_block_group_nr;       /* block group # of this sb */
>         3c:       s_feature_compat;       /* compatible feature set */
>        242:       s_feature_incompat;     /* incompatible feature set */
>         7b:       s_feature_ro_compat;    /* readonly-compatible fea...
>          0:       s_algorithm_usage_bitmap; /* For compression */
>          0:       s_prealloc_blocks;      /* Nr of blocks to try to ...
>          0:       s_prealloc_dir_blocks;  /* Nr to preallocate for ...
>   df010000:       s_padding1;
>    8000000:       s_journal_inum;         /* inode number of journal ...
>          0:       s_journal_dev;          /* device number of journal...
>          0:       s_last_orphan;          /* start of list of inodes ...
>   f806edbf:       s_hash_seed[4];         /* HTREE hash seed */
>          1:       s_def_hash_version;     /* Default hash version to ...
>          1:       s_reserved_char_pad;
>          0:       s_reserved_word_pad;
>          c:       s_default_mount_opts;
>          0:       s_first_meta_bg;        /* First metablock block gr...
>   1407edbf:       s_reserved[190];        /* Padding to the end of ...
>
>   1+0 records in
>   1+0 records out
>   512 bytes (512 B) copied, 0.000568372 s, 901 kB/s
> 
> In conclusion, I have 1837 superblocks - they are all essentially
> identical - and unequal to the surrounding blocks, but they're at an
> offset that I can't pass to any of the e2 programs.
> 
> That's why it occurred to me that there must be some other similar
> structures laying around, e.g. the Group Descriptor Tables to help me
> get oriented.
> 
> I also tried this:
> 
> $ sudo dumpe2fs -o superblock=$((206983138/2)) -o blocksize=1024
> /dev/sdc1 dumpe2fs 1.41.11 (14-Mar-2010)
> dumpe2fs: Filesystem has unexpected block size while trying to open
> /dev/ sdc1
> Couldn't find valid filesystem superblock.
> 
> Thanks for your interest!
> cts

Back to comp.os.linux.misc | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Recovering an EXT3 FS - hopeless if inode list is overwritten? "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2015-05-22 08:05 +0000
  Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? Tim Watts <tw_usenet@dionic.net> - 2015-05-22 09:24 +0100
  Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? Michael Baeuerle <michael.baeuerle@stz-e.de> - 2015-05-22 08:38 +0000
    Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2015-05-22 09:58 +0000
    Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2015-07-12 12:54 +0000
      Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2015-07-12 12:47 -0400
        Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2015-07-13 07:40 +0000
          Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2015-07-13 14:30 -0400
      Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? Michael Baeuerle <michael.baeuerle@stz-e.de> - 2015-07-13 11:41 +0000
        Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2015-07-13 20:37 +0000
          Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2015-07-14 07:55 +0000
          Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? Michael Baeuerle <michael.baeuerle@stz-e.de> - 2015-07-14 14:35 +0000
            Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2015-07-14 15:20 +0000
  Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? Vilmos Soti <vilmos@soti.ca> - 2015-05-22 10:53 -0700
    Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2015-05-23 08:25 +0000
    Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? Unknown <dog@gmail.com> - 2015-05-25 06:40 +0000
  Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? lakshmi <lakshmipathi.g@gmail.com> - 2015-05-25 22:06 -0700
    Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? Jean-David Beyer <jeandavid8@verizon.net> - 2015-05-26 09:57 -0400
      Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? Robert Riches <spamtrap42@jacob21819.net> - 2015-05-27 02:58 +0000
        Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2015-06-04 06:17 +0000
          Re: Recovering an EXT3 FS - hopeless if inode list is overwritten? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2015-06-04 18:44 +0000

csiph-web