From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: Corrupt ext2/ext3 directory entries not recovered by e2fsck
Date: Sat, 13 Oct 2001 22:59:09 +1000 [thread overview]
Message-ID: <17538.1002977949@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sat, 13 Oct 2001 22:44:34 +1000." <17469.1002977074@ocs3.intra.ocs.com.au>
On Sat, 13 Oct 2001 22:44:34 +1000,
Keith Owens <kaos@ocs.com.au> wrote:
>The filesystem was created as ext3 but is currently being accessed as
>ext2 while I work on XFS and kdb for IA64. After multiple power rests,
>several directory entries are corrupt. Attempts to access the files
>get I/O error with nothing in the log. Running e2fsck does not correct
>the broken directory entry, neither does booting a kernel that supports
>ext3.
I forgot to mention that both fsck.ext2 and fsck.ext3 report
1: Entry 'sendmail.pid' in /var/run (686849) has deleted/unused inode 688415. CLEARED.
/1: Entry 'crond.pid' in /var/run (686849) has deleted/unused inode 688416. CLEARED.
/1: Entry 'xfs.pid' in /var/run (686849) has deleted/unused inode 688417. CLEARED.
/1: Entry 'atd.pid' in /var/run (686849) has deleted/unused inode 688418. CLEARED.
but the entries are still corrupt.
next prev parent reply other threads:[~2001-10-13 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 12:44 Corrupt ext2/ext3 directory entries not recovered by e2fsck Keith Owens
2001-10-13 12:59 ` Keith Owens [this message]
2001-10-13 19:46 ` Bernd Eckenfels
-- strict thread matches above, loose matches on Subject: below --
2001-10-13 14:06 Manfred Spraul
2001-10-13 15:02 ` Keith Owens
2001-10-13 19:09 ` Oliver Xymoron
2001-10-14 1:15 ` Keith Owens
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=17538.1002977949@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@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.