From: "kyle" <kylewong@southa.com>
To: <linux-ext4@vger.kernel.org>
Subject: need help with getting into a corrupted sub directory
Date: Sat, 30 Jan 2010 14:07:50 +0800 [thread overview]
Message-ID: <004d01caa172$8d846c10$6401a8c0@kyle> (raw)
Hi,
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.
Now, my ext3 fs is /dev/sde2
I can mount it without any error:
mount /dev/sde2 /tmp
then, I can 'cd' into /tmp to get a sub directory listing.
let's says there's
Hello
World
users
public
now when I do 'ls public', 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: Input/output error
'sde' will disappeared from the system, need power off / on can get it back.
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" ?
Thanks a lot,
kyle
next reply other threads:[~2010-01-30 6:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 6:07 kyle [this message]
2010-01-30 7:24 ` need help with getting into a corrupted sub directory Andreas Dilger
2010-01-30 17:44 ` tytso
2010-01-31 18:11 ` Andreas Dilger
2010-02-01 4:08 ` kyle
2010-02-01 4:08 ` kyle
2010-02-09 15:51 ` 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='004d01caa172$8d846c10$6401a8c0@kyle' \
--to=kylewong@southa.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 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.