Today our server had seriuos problems, we had to reinitiate it and run fsck
manually.
Dou you think it's an ext3, kernel (vanilla 2.4.19) or hardware bug?
The errors were (from syslog):
--------------------------------
Oct 6 16:10:25 nou kernel: attempt to access beyond end of device
Oct 6 16:10:25 nou kernel: 72:02: rw=0, want=230266240, limit=4882432
Oct 6 16:10:25 nou kernel: attempt to access beyond end of device
Oct 6 16:10:25 nou kernel: 72:02: rw=0, want=1371661772, limit=4882432
Oct 6 16:10:25 nou kernel: attempt to access beyond end of device
Oct 6 16:10:25 nou kernel: 72:02: rw=0, want=1301647364, limit=4882432
Oct 6 16:10:25 nou kernel: attempt to access beyond end of device
Oct 6 16:10:25 nou kernel: 72:02: rw=0, want=230266240, limit=4882432
Oct 6 16:10:25 nou kernel: attempt to access beyond end of device
Oct 6 16:10:25 nou kernel: 72:02: rw=0, want=1371661772, limit=4882432
Oct 6 16:10:25 nou kernel: attempt to access beyond end of device
Oct 6 16:10:25 nou kernel: 72:02: rw=0, want=1371661772, limit=4882432
Oct 6 16:10:25 nou kernel: attempt to access beyond end of device
Oct 6 16:10:25 nou kernel: 72:02: rw=0, want=1371661772, limit=4882432
Oct 6 16:10:25 nou kernel: EXT3-fs error (device ataraid(114,2)):
ext3_free_inode: bit already cleared for inode 210865
Oct 6 16:10:25 nou kernel: Aborting journal on device ataraid(114,2).
Oct 6 16:10:25 nou kernel: Remounting filesystem read-only
Oct 6 16:10:25 nou kernel: EXT3-fs error (device ataraid(114,2)) in
ext3_delete_inode: IO failure
Oct 6 16:10:25 nou kernel: EXT3-fs error (device ataraid(114,2)) in
start_transaction: Journal has aborted
Oct 6 16:10:25 nou kernel: EXT3-fs error (device ataraid(114,2)) in
ext3_delete_inode: Journal has aborted
Oct 6 16:10:25 nou kernel: EXT3-fs error (device ataraid(114,2)) in
start_transaction: Journal has aborted
Oct 6 16:10:25 nou kernel: EXT3-fs error (device ataraid(114,2)) in
ext3_delete_inode: Journal has aborted
Oct 6 16:12:36 nou kernel: EXT3-fs error (device ataraid(114,2)) in
start_transaction: Journal has aborted
--------------------------------------
nou:~# mount
/dev/ataraid/d0p2 on / type ext3 (rw,noatime,errors=remount-ro)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/ataraid/d0p1 on /boot type ext2 (rw)
/dev/ataraid/d0p5 on /home type ext3 (rw,noatime,data=writeback)
nou:~# cat /proc/partitions
major minor #blocks name
114 0 19551136 ataraid/d0
114 1 14320 ataraid/d0p1
114 2 4882432 ataraid/d0p2
114 3 1 ataraid/d0p3
114 5 14153712 ataraid/d0p5
114 6 499696 ataraid/d0p6
34 0 19551168 hdg
34 1 14320 hdg1
34 2 4882432 hdg2
34 3 1 hdg3
34 5 14153712 hdg5
34 6 499696 hdg6
33 0 19551168 hde
33 1 14320 hde1
33 2 4882432 hde2
33 3 1 hde3
33 5 14153712 hde5
33 6 499696 hde6
00:00.0 Host bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266] (rev 01)
Subsystem: Super Micro Computer Inc: Unknown device 2166
Flags: bus master, medium devsel, latency 8
Memory at f0000000 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 2.0
Capabilities: [c0] Power Management version 2
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] (prog-if
00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000a000-0000afff
Memory behind bridge: f4000000-f6ffffff
Capabilities: [80] Power Management version 2
00:0c.0 RAID bus controller: Promise Technology, Inc. 20267 (rev 02)
Subsystem: Promise Technology, Inc. Fasttrak100
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at b000 [size=8]
I/O ports at b400 [size=4]
I/O ports at b800 [size=8]
I/O ports at bc00 [size=4]
I/O ports at c000 [size=64]
Memory at f8100000 (32-bit, non-prefetchable) [size=128K]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [58] Power Management version 1
Regards,
--
ricardo galli
_______________________________________________
Ext3-users@redhat.com
https://listman.redhat.com/mailman/listinfo/ext3-users
