mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kyle Wong" <kylewong@southa.com>
To: <linux-kernel@vger.kernel.org>
Subject: bug ? ext3-fs error with kernel 2.6.17
Date: Thu, 3 Aug 2006 16:41:56 +0800	[thread overview]
Message-ID: <008901c6b6d8$bef29d40$9d02a8c0@kyle> (raw)

Hi,

Today one of my machine got the following error and the filesystem was
remounted as read-only automatically:

Aug  3 14:24:09 localhost kernel: EXT3-fs error (device md2): ext3_readdir:
bad entry in directory #48170704: rec_len is smaller than minimal -
offset=0, inode=0, rec_len=0, name_len=0
Aug  3 14:24:09 localhost kernel: Aborting journal on device md2.
Aug  3 14:24:09 localhost kernel: ext3_abort called.
Aug  3 14:24:09 localhost kernel: EXT3-fs error (device md2):
ext3_journal_start_sb: Detected aborted journal
Aug  3 14:24:09 localhost kernel: Remounting filesystem read-only
Aug  3 14:24:09 localhost kernel: __journal_remove_journal_head: freeing
b_committed_data
Aug  3 14:24:09 localhost kernel: __journal_remove_journal_head: freeing
b_committed_data

My machine is running with a AMD x86_64 CPU, 3GB Ram and 10 Seagate harddisk
in MD raid 5 mode. Kernel is 64bits 2.6.17
The MD raid 5 did not report any problem and my server log does not contain
any error about libata and md. It just show the above ext3 errors.
The affected filesystem is around 1 month old and never have any error and
crash before.
I need to umount the affected ext3 volume and remount it to take it back to
read write mode.

Please cc me if possible, I'm not subscribed. Thanks.

Kyle





                 reply	other threads:[~2006-08-03  8:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='008901c6b6d8$bef29d40$9d02a8c0@kyle' \
    --to=kylewong@southa.com \
    --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

Powered by JetHome