[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <27FC5E2E-2F85-478A-95F2-1B9ED9D07690@sun.com>
Date: Sat, 30 Jan 2010 00:24:09 -0700
From: Andreas Dilger <adilger@....com>
To: kyle <kylewong@...tha.com>
Cc: linux-ext4@...r.kernel.org
Subject: Re: need help with getting into a corrupted sub directory
On 2010-01-29, at 23:07, kyle wrote:
> I have a ext3 filesystem created inside a problematic seagate
> ST3500320AS
> drive. The drive will just shut itself down automatically whenever
> it hits
> any read error. Only way to wake it up it to cold power off / on the
> computer.
Strange, I had to do the same for a friend, and I think it was the
same drive.
You should put it into a USB enclosure - it speeds things up a lot.
> 'sde' will disappeared from the system, need power off / on can get
> it back.
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.
> After cold boot, I know there's a subdirectory called "EL" inside
> "public",
> if I do a 'ls public/EL',
> I get:
> EXT3-fs error (device sde2): ext3_get_inode_loc: unable to read inode
> block - inode: 26181633, block=26181634
> ls: cannot access /tmp/public/EL: Input/output error
>
> Is there any way I can get into subdirectory of "public" without the
> need of
> read inode block 26181633/26181634 ?
> Is it still possible to get a full subdirectory listing of "public" ?
debugfs is your friend. It can open and list a directory by inode
number, and dump the files to another filesystem.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
--
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
Powered by blists - more mailing lists