From: Florian Weimer <fw@deneb.enyo.de>
To: linux-kernel@vger.kernel.org
Subject: [2.5.69] ext3 error: rec_len %% 4 != 0
Date: Wed, 28 May 2003 10:05:07 +0200 [thread overview]
Message-ID: <8765nva43w.fsf@deneb.enyo.de> (raw)
Sometimes, our 2.5 test machine (actually, it's a production machine,
please don't ask why we can't use 2.4 *sigh*) stops with an ext3 error
message. We have now activated proper logging, and that's what we
got:
May 28 03:23:00 kernel: EXT3-fs error (device md0): ext3_readdir: bad entry in directory #16056745: rec_len %% 4 != 0 - offset=52, inode=431743, rec_len=37017, name_len=41
May 28 03:23:00 kernel: Aborting journal on device md0.
May 28 03:23:00 kernel: ext3_abort called.
May 28 03:23:00 kernel: EXT3-fs abort (device md0): ext3_journal_start: Detected aborted journal
May 28 03:23:00 kernel: Remounting filesystem read-only
May 28 03:23:00 kernel: EXT3-fs error (device md0) in ext3_commit_write: IO failure
May 28 03:23:00 kernel: EXT3-fs error (device md0) in start_transaction: Journal has aborted
What could cause this? Spurious data transmission errors? md0 is a
RAID-5, the machine is a Siemens Primergy H450 (Quad Pentium 4/Xeon, 4
GB RAM, two-channel Adaptec aic7899 Ultra160 SCSI adapter).
According to fsck.ext3, the on-disk data structures are clean, and if
I run "find" across the file system after the reboot, it doesn't
complain about bad directory entries, either.
next reply other threads:[~2003-05-28 7:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 8:05 Florian Weimer [this message]
2003-05-28 8:25 ` [2.5.69] ext3 error: rec_len %% 4 != 0 Andrew Morton
2003-05-28 8:50 ` Florian Weimer
2003-05-28 8:59 ` Andrew Morton
2003-05-30 15:15 ` Florian Weimer
2003-06-06 7:59 ` Florian Weimer
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=8765nva43w.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--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