Hallo Allerseits
Habe hier nen Server der seit über 1 Jahr ohne Probleme läuft.
Seit heute habe ich schon 2 Kernelpanics.
Folgende Meldung erscheint bevor das System steh bleibt:
Message from syslogd@gigsy at Sun Jun 22 10:47:51 2003 ...
gigsy kernel: journal-601, buffer write failed
Für mich sieht es nach einem Problem mit Reiserfs aus...
Zu meinem System:
ASUS TX97-XE
AMDK6 III 400
256 MB
IBM IBM-DTTA-351010 (10GB)
IBM/Hitachi IC35L060AVV207-0 (60GB)
SuSE 8.0 Pro + Updates
Das System ist wie folgt partitioniert:
/dev/hda3 / reiserfs
/dev/hda1 /boot ext2
/dev/hdb1 /d01 reiserfs
/dev/hdb2 /d02 reiserfs
/home ist auf /d01 (symlink)
Seit einiger Zeit habe ich noch folgende Bootmeldung:
<4>reiserfs: checking transaction log (device 03:03) ...
<4>Warning, log replay starting on readonly filesystem
<4>reiserfs: replayed 62 transactions in 12 seconds
<4>Using r5 hash to sort names
<4>ReiserFS version 3.6.25
<4>VFS: Mounted root (reiserfs filesystem) readonly.
<4>change_root: old root has d_count=2
<5>Trying to unmount old root ... okay
<4>Freeing unused kernel memory: 120k freed
<6>Universal TUN/TAP device driver 1.4 (C)1999-2001 Maxim Krasnyansky
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<4>clm-6006: writing inode 938 on readonly FS
<6>md: Autodetecting RAID arrays.
<6>md: autorun ...
<6>md: ... autorun DONE.
<4>clm-6005: writing inode 938 on readonly FS
<4>Removing [410 100734 0x0 SD]..<4>done
<4>Removing [17804 99668 0x0 SD]..<4>done
<4>There were 2 uncompleted unlinks/truncates. Completed
<6>LVM version 1.0.3(19/02/2002) module loaded
<6>Adding Swap: 133048k swap-space (priority 42)
<4>clm-6005: writing inode 24057 on readonly FS
<4>clm-6005: writing inode 538 on readonly FS
<4>clm-6005: writing inode 14555 on readonly FS
<4>clm-6005: writing inode 14556 on readonly FS
<4>clm-6005: writing inode 14511 on readonly FS
<4>clm-6005: writing inode 14553 on readonly FS
<4>clm-6005: writing inode 11921 on readonly FS
<4>clm-6005: writing inode 11922 on readonly FS
<4>clm-6005: writing inode 162182 on readonly FS
<4>clm-6005: writing inode 24053 on readonly FS
<4>clm-6005: writing inode 14763 on readonly FS
<4>reiserfs: checking transaction log (device 03:41) ...
<4>reiserfs: replayed 24 transactions in 2 seconds
<4>Using r5 hash to sort names
<4>ReiserFS version 3.6.25
<4>reiserfs: checking transaction log (device 03:42) ...
<4>Using r5 hash to sort names
<4>ReiserFS version 3.6.25
Kernel logging (ksyslog) stopped.
Kernel log daemon terminating.
Hat Jemand eine Idee woran es liegen könnte?
Danke!
MfG
Alexander
--
Alex Ge