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 <[email protected]>
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]