RE: Kernel 2.4.9 and ABOVE

OK. I started up 2.4.18 now... That's what I get on the screen while
working with the kernel (re-compiling kernel 2.4.18 with ext3):
EXT2-fs error (device sd(8,18)): ext2_free_blocks: bit already cleared
for block 1607000
EXT2-fs error (device sd(8,18)): ext2_free_blocks: bit already cleared
for block 1607001
EXT2-fs error (device sd(8,18)): ext2_free_blocks: bit already cleared
for block 1607002
EXT2-fs error (device sd(8,18)): ext2_free_blocks: Freeing blocks in
system zones - Block = 1605635, count = 5
EXT2-fs error (device sd(8,18)): ext2_free_blocks: bit already cleared
for block 1607979
EXT2-fs error (device sd(8,18)): ext2_free_blocks: bit already cleared
for block 1607980
EXT2-fs error (device sd(8,18)): ext2_new_block: Allocating block in
system zone - block = 1605635
EXT2-fs error (device sd(8,18)): ext2_free_blocks: Freeing blocks in
system zones - Block = 1605637, count = 6
EXT2-fs error (device sd(8,18)): ext2_free_blocks: bit already cleared
for block 1607839
EXT2-fs error (device sd(8,18)): ext2_free_blocks: bit already cleared
for block 1607840
EXT2-fs error (device sd(8,18)): ext2_free_blocks: bit already cleared
for block 1607841
EXT2-fs error (device sd(8,18)): ext2_free_blocks: bit already cleared
for block 1607842
EXT2-fs error (device sd(8,18)): ext2_new_block: Allocating block in
system zone - block = 1605637
EXT2-fs error (device sd(8,18)): ext2_free_blocks: Freeing blocks in
system zones - Block = 1605641, count = 4

This isn't normal I guess!!!!

HELP!!!

-Oliver

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Peter 
> Leif Rasmussen (PLR)
> Sent: Tuesday, April 09, 2002 12:06 PM
> To: '[email protected]'
> Subject: RE: Kernel 2.4.9 and ABOVE
> 
> 
> OK, I haven't tried to 'kick' my alpha yet with the 2.4.18 
> kernel and actually only booted with it once since it hasn't 
> been down since.
> 
> Using ext2 as FS (I'm planning to change to ext3 in the 
> future, at least for
> /) I have before seen so many fsck errors during boot after a 
> 'kick' (I never myself kicked it, but using IDE disks from 
> IBM, Travelstar, with the Multia was a bad idea so I went 
> with much more expensive SCSI disks) that the automatic 
> boottime fsck wouldn't continue, but entering single user 
> mode and doing manual fsck always enabled me to get back and running.
> 
> I'm not sure if 2.4.17 was so good, but 2.4.18 has been 
> rocksolid til now. The basesystem is RH7.1.
> 
> > -----Original Message-----
> > From: Oliver Pitzeier [mailto:[email protected]]
> > Sent: 9. april 2002 11:54
> > To: [email protected]
> > Subject: RE: Kernel 2.4.9 and ABOVE
> > 
> > 
> > Leif Rasmussen wrote:
> > > I have 2.4.18 running on a UDB/Multia running as a
> > > web/mail-server (incl. development of cgi binaries for the 
> > > webserver) and it now has uptime >20 days and no corruption 
> > at all :-)
> > 
> > That's nice to hear!!!
> > 
> > So the problem is the following:
> > I have got 2 Compaq Alpha (Model DS10) with SCSI-Harddrives. 
> > Everything seems to be fine using kernel 2.4.17 and 2.4.18, 
> but if I 
> > _kick_ the machine... I mean poweroff without shutting down the 
> > system. I get a lot of fsck errors and afterwards the system is no 
> > longer bootable!!!
> > 
> > It's maybe my problem, but I also wonder why RedHat is not 
> releasing a 
> > newer kernel package for their distribution. Via up2date I only get 
> > 2.4.9...
> > 
> > Best regards,
> >  Oliver
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Axp-kernel-list mailing list
> > [email protected] 
> > https://listman.redhat.com/mailman/listinfo/axp-kernel-list
> > 
> 
> 
> 
> _______________________________________________
> Axp-kernel-list mailing list
> [email protected] 
> https://listman.redhat.com/mailman/listinfo/ax> p-kernel-list
>