From: Ben Greear <greearb@candelatech.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: ext3 file system went read-only in 2.6.18.2 (plus hacks)
Date: Mon, 08 Jan 2007 13:38:34 -0800 [thread overview]
Message-ID: <45A2B9DA.20104@candelatech.com> (raw)
First, this kernel is tainted by one of my proprietary patches
and also has my other non-proprietary patches applied, so please
ignore as you wish. My patches do not (purposefully) affect the file-system.
The system is a via/c3 system running a fairly stripped down FC5
installation on a 1GB CF disk. We've been using this platform
for over a year and this is the first file system error we've
seen. It could easily be that the CF is funky, but I thought
I'd post the message in case it proves to be something else.
eth1: Promiscuous mode enabled.
eth1: Promiscuous mode enabled.
EXT3-fs error (device hda1): ext3_find_entry: bad entry in directory #99247: rec_len % 4 1
Aborting journal on device hda1.
EXT3-fs error (device hda1): ext3_find_entry: bad entry in directory #99254: rec_len % 4 1
ext3_abort called.
EXT3-fs error (device hda1): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device hda1): ext3_find_entry: bad entry in directory #99048: rec_len % 4 1
EXT3-fs error (device hda1): ext3_find_entry: bad entry in directory #99041: directory en1
syslogd: /var/log/messages: Read-only file system
syslogd: /var/log/secure: Read-only file system
syslogd: /var/log/maillog: Read-only file system
syslogd: /var/log/cron: Read-only file system
syslogd: /var/log/spooler: Read-only file system
syslogd: /var/log/boot.log: Read-only file system
syslogd: /var/log/messages: Read-only file system
syslogd: /var/log/secure: Read-only file system
syslogd: /var/log/maillog: Read-only file system
syslogd: /var/log/cron: Read-only file system
syslogd: /var/log/spooler: Read-only file system
syslogd: /var/log/boot.log: Read-only file system
pktgen: pktgen_mark_device marking eth0#5 for removal
pktgen: pktgen_mark_device marking eth0#0 for removal
.....
After restarting and a manual fsck, the system appears to
be back to normal.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2007-01-08 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 21:38 Ben Greear [this message]
2007-01-08 22:05 ` ext3 file system went read-only in 2.6.18.2 (plus hacks) Alan
2007-01-08 22:18 ` Ben Greear
2007-01-08 22:53 ` Theodore Tso
2007-01-08 23:00 ` Ben Greear
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=45A2B9DA.20104@candelatech.com \
--to=greearb@candelatech.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