lkml.org 
[lkml]   [2007]   [Jan]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subjectext3 file system went read-only in 2.6.18.2 (plus hacks)
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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-01-08 23:07    [W:0.073 / U:0.100 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site