From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Corrupt ext2/ext3 directory entries not recovered by e2fsck
Date: Sat, 13 Oct 2001 22:44:34 +1000 [thread overview]
Message-ID: <17469.1002977074@ocs3.intra.ocs.com.au> (raw)
IA64, gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-95). Various
kernels from 2.4.9 (with ext3) through 2.4.13-pre1 (with XFS).
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 am surprised that neither ext3 recovery nor e2fsck detected the
broken directory entries. Before I clri the directory entry, does
anybody want more details?
debugfs: ls -l /var/run
686849 40755 0 0 4096 13-Oct-2001 21:41 .
179873 40755 0 0 4096 25-Sep-2001 11:39 ..
507431 40775 0 0 4096 27-Jul-2001 07:32 netreport
686888 100664 0 22 4800 13-Oct-2001 21:45 utmp
376417 40755 75 75 4096 9-Jul-2001 21:40 radvd
654934 40700 0 0 4096 24-Jul-2001 02:52 sudo
686995 100644 0 0 11 13-Oct-2001 21:41 runlevel.dir
687119 100600 0 0 4 13-Oct-2001 21:41 syslogd.pid
687120 100600 0 0 4 13-Oct-2001 21:41 klogd.pid
688413 100644 0 0 4 13-Oct-2001 21:41 sshd.pid
688414 100644 0 0 4 13-Oct-2001 21:41 xinetd.pid
2133571369 --- error --- sendmail.pid
2133571369 --- error --- crond.pid
2133571369 --- error --- xfs.pid
2133571369 --- error --- atd.pid
Dump of the directory.
0000 01 7B 0A 00 0C 00 01 02 2E 00 00 00 A1 BE 02 00 * .{..........¡... *
0010 0C 00 02 02 2E 2E 00 00 27 BE 07 00 14 00 09 02 * ........'....... *
0020 6E 65 74 72 65 70 6F 72 74 00 00 00 28 7B 0A 00 * netreport...({.. *
0030 0C 00 04 01 75 74 6D 70 61 BE 05 00 10 00 05 02 * ....utmpa....... *
0040 72 61 64 76 64 00 00 00 56 FE 09 00 0C 00 04 02 * radvd...V....... *
0050 73 75 64 6F 93 7B 0A 00 14 00 0C 01 72 75 6E 6C * sudo.{......runl *
0060 65 76 65 6C 2E 64 69 72 0F 7C 0A 00 14 00 0B 01 * evel.dir.|...... *
0070 73 79 73 6C 6F 67 64 2E 70 69 64 00 10 7C 0A 00 * syslogd.pid..|.. *
0080 14 00 09 01 6B 6C 6F 67 64 2E 70 69 64 00 00 00 * ....klogd.pid... *
0090 1D 81 0A 00 10 00 08 01 73 73 68 64 2E 70 69 64 * ........sshd.pid *
00a0 1E 81 0A 00 14 00 0A 01 78 69 6E 65 74 64 2E 70 * ........xinetd.p *
00b0 69 64 00 00 00 00 00 00 14 00 0C 01 73 65 6E 64 * id..........send *
00c0 6D 61 69 6C 2E 70 69 64 00 00 00 00 14 00 09 01 * mail.pid........ *
00d0 63 72 6F 6E 64 2E 70 69 64 00 00 00 00 00 00 00 * crond.pid....... *
00e0 10 00 07 01 78 66 73 2E 70 69 64 00 00 00 00 00 * ....xfs.pid..... *
00f0 14 0F 07 01 61 74 64 2E 70 69 64 00 00 00 00 00 * ....atd.pid..... *
0100 04 0F 0C 01 73 68 75 74 64 6F 77 6E 2E 70 69 64 * ....shutdown.pid *
0110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 * ................ *
next reply other threads:[~2001-10-13 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 12:44 Keith Owens [this message]
2001-10-13 12:59 ` Keith Owens
2001-10-13 19:46 ` Bernd Eckenfels
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=17469.1002977074@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®