Hello,
I've a machine running Linux 2.4.20 and which is displaying
these on the console :
EXT2-fs error (device sd(8,18)): ext2_write_inode: unable to read inode
block - inode=549972, block=1081642
EXT2-fs error (device sd(8,18)): read_block_bitmap: Cannot read block
bitmap - block_group = 39, block_bitmap = 1277952
EXT2-fs error (device sd(8,9)): ext2_write_inode: unable to read inode
block - inode=12310, block=49166
EXT2-fs error (device sd(8,9)): ext2_write_inode: unable to read inode
block - inode=12311, block=49166
EXT2-fs error (device sd(8,9)): ext2_write_inode: unable to read inode
block - inode=38852, block=155665
EXT2-fs error (device sd(8,9)): ext2_write_inode: unable to read inode
block - inode=38856, block=155665
EXT2-fs error (device sd(8,18)): ext2_write_inode: unable to read inode
block - inode=541026, block=1081363
....
Not only that, but also trying to run commands results in
Input/Output error :
bash-2.05# umount /dev/sda5
bash: /bin/umount: Input/output error
bash-2.05# reboot
EXT2-fs error (device sd(8,5)): ext2_write_inode: unable to read inode
block - inode=163903, block=327685
bash: /usr/bin/reboot: Input/output error
What's going on ?
Here is a copy of /etc/fstab and /proc/partitions
bash-2.05# cat fstab
LABEL=/ / ext2 defaults
1 1
LABEL=/boot /boot ext2 defaults
1 2
none /dev/pts devpts gid=5,mode=620
0 0
none /proc proc defaults
0 0
#none /dev/shm tmpfs defaults
0 0
LABEL=/tmp /tmp ext2 defaults
1 2
LABEL=/u01 /u01 ext2 defaults
1 2
LABEL=/usr /usr ext2 defaults
1 2
LABEL=/var /var ext2 defaults
1 2
/dev/sdb2 /u02 ext2 defaults
1 2
/dev/sdc2 /u03 ext2 defaults
1 2
/dev/sda3 swap swap defaults
0 0
/dev/sdb1 swap swap defaults
0 0
/dev/sdc1 swap swap defaults
0 0
/dev/cdrom /mnt/cdrom iso9660
noauto,owner,kudzu,ro 0 0
/dev/fd0 /mnt/floppy auto
noauto,owner,kudzu 0 0
major minor #blocks name rio rmerge rsect ruse wio wmerge wsect
wuse running use aveq
8 0 71678592 sda 66321 115222 1268480 2207070 161924 256121
3116304 14942220 0 1429590 17149230
8 1 32098 sda1 6 18 48 10 0 0 0 0 0 10 10
8 2 265072 sda2 63 563 1252 390 5 2 14 130 0 250 520
8 3 2096482 sda3 2 0 16 0 0 0 0 0 0 0 0
8 4 1 sda4 0 0 0 0 0 0 0 0 0 0 0
8 5 2096451 sda5 23516 1667 201458 7340 27444 4226 254272
58440 0 16830 65780
8 6 3148708 sda6 13903 1304 121410 25570 6445 1165 61528
13290140 0 229230 13315720
8 7 62942638 sda7 15418 95200 884530 2060070 106142 234338
2723840 482270 0 1382240 2542270
8 8 522081 sda8 38 33 142 130 264 2376 5280 4510 0 870 4640
8 9 522081 sda9 13368 16416 59568 113500 21624 14014 71370
1106730 0 275560 1220220
8 16 71678592 sdb 130838 413501 4354274 595520 267920 430758
5596704 751240 0 599880 1347600
8 17 2096482 sdb1 2 0 16 0 0 0 0 0 0 0 0
8 18 69577515 sdb2 130835 413498 4354250 595520 267920 430758
5596704 751250 0 599860 1347580
8 32 71678592 sdc 60418 1417060 3184236 259440 69082 181066
1987874 1994140 0 365330 2253500
8 33 2096482 sdc1 2 0 16 0 0 0 0 0 0 0 0
8 34 69577515 sdc2 60415 1417057 3184212 259440 69082 181066
1987874 1994140 0 365330 2253500
Could someone help me ?
Regards,
Paul
Paul, [email protected]
> I've a machine running Linux 2.4.20 and which is displaying
> these on the console :
Has this only just started happening, or has the machine never worked
with 2.4.20? What about older 2.4 kernels?
John
Not very sure about it....
I got it before with 2.4.18 but sometime got a crash (kernel oops),
so I upgraded kernel to 2.4.20, put a remote console on the machine
to control and got that... but when it has been initially powered
with 2.4.20, it seems it was fine... and it started later as I
now got them.
This is one of the reason I wanted to restart it, but as reboot
is not accessible, I need to wait sometime...
Paul
> > I've a machine running Linux 2.4.20 and which is displaying
> these on
> > the console :
>
> Has this only just started happening, or has the machine
> never worked with 2.4.20? What about older 2.4 kernels?
>
> John
>
Hmmmm.... One point that may be of interest :
root 2 0.0 0.0 0 0 ? SW Jan31 0:00 [keventd]
root 3 0.0 0.0 0 0 ? SWN Jan31 0:00
[ksoftirqd_CPU0]
root 4 0.0 0.0 0 0 ? SWN Jan31 0:00
[ksoftirqd_CPU1]
root 5 0.0 0.0 0 0 ? SWN Jan31 0:00
[ksoftirqd_CPU2]
root 6 0.0 0.0 0 0 ? SWN Jan31 0:00
[ksoftirqd_CPU3]
root 7 0.0 0.0 0 0 ? SW Jan31 0:00 [kswapd]
root 8 0.0 0.0 0 0 ? SW Jan31 0:00 [bdflush]
root 9 6.3 0.0 0 0 ? SW Jan31 124:10
[kupdated]
root 10 0.0 0.0 0 0 ? SW Jan31 0:00 [aacraid]
root 11 0.0 0.0 0 0 ? SW Jan31 0:00
[scsi_eh_0]
root 508 0.0 0.0 1480 624 ? S Jan31 0:55 syslogd
-m 0
ntp 628 0.0 0.0 1936 1932 ? SL Jan31 0:13 ntpd -U
ntp
root 651 0.0 0.0 2936 1192 ? S Jan31 0:00
/usr/sbin/sshd
root 683 0.0 0.0 2228 932 ? S Jan31 0:00 xinetd
-stayalive -reuse -pidfile /var/run/xinetd.pid
root 743 0.0 0.0 1460 620 ? S Jan31 0:00 crond
daemon 761 0.0 0.0 1448 572 ? S Jan31 0:00
/usr/sbin/atd
root 891 0.0 0.0 1388 452 tty1 S Jan31 0:00
/sbin/mingetty tty1
root 892 0.0 0.0 1388 452 tty2 S Jan31 0:00
/sbin/mingetty tty2
root 893 0.0 0.0 1388 452 tty3 S Jan31 0:00
/sbin/mingetty tty3
root 894 0.0 0.0 1392 456 tty4 S Jan31 0:00
/sbin/mingetty tty4
root 895 0.0 0.0 1392 452 tty5 S Jan31 0:00
/sbin/mingetty tty5
root 896 0.0 0.0 1384 448 tty6 S Jan31 0:00
/sbin/mingetty tty6
root 6127 0.0 0.0 2300 1124 ttyS0 S 11:06 0:00 login --
rol
rol 6839 0.0 0.0 2904 1504 ttyS0 S 14:20 0:11 -tcsh
root 6861 0.0 0.0 2312 992 ttyS0 S 14:21 0:00 su root
root 6862 0.5 0.0 2524 1436 ttyS0 S 14:21 1:39 bash
root 8199 0.0 0.0 2636 728 ttyS0 R 19:44 0:00 ps
auxwwww
Very high CPU usage for kupdated.... Could this explain ?
Paul
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Paul Rolland
> Sent: Saturday, February 01, 2003 4:26 PM
> To: 'John Bradford'
> Cc: [email protected]
> Subject: Re: Linux 2.4.20 - Bunch of EXT2-fs error
>
>
> Not very sure about it....
> I got it before with 2.4.18 but sometime got a crash (kernel
> oops), so I upgraded kernel to 2.4.20, put a remote console
> on the machine to control and got that... but when it has
> been initially powered with 2.4.20, it seems it was fine...
> and it started later as I now got them.
>
> This is one of the reason I wanted to restart it, but as
> reboot is not accessible, I need to wait sometime...
>
> Paul
>
> > > I've a machine running Linux 2.4.20 and which is displaying
> > these on
> > > the console :
> >
> > Has this only just started happening, or has the machine
> > never worked with 2.4.20? What about older 2.4 kernels?
> >
> > John
> >
>
> -
> 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/