linux-ext4 - Re: need help with getting into a corrupted sub directory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 9 Feb 2010 16:51:07 +0100
From:	Jan Kara <jack@...e.cz>
To:	kyle <kylewong@...tha.com>
Cc:	Andreas Dilger <adilger@....com>, linux-ext4@...r.kernel.org
Subject: Re: need help with getting into a corrupted sub directory

> >
> > To get most of the data off the dying drive, use rsync -v, and create
> > a list
> > of files to exclude, when you detect they cause the drive to die.
> 
> I need to get files from 'public/EL/', however, 'public' cause the drive die
> ........
> 
> >
> >
> > debugfs is your friend.  It can open and list a directory by inode
> > number, and dump the files to another filesystem.
> 
> Is it possible to get the inode number of 'public/EL' without hitting the
> 'public' which cause the drive die?
  Not easily. But as Ted pointed out, you might try to dd blocks from /dev/sde
upto the problematic block and then next time starting after the problematic block.
If this works out, you can then just run fsck at the resulting image and it should
recover the filesystem reasonably...

									Honza
-- 
Jan Kara <jack@...e.cz>
SuSE CR Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html