* RE: Kernel 2.4.9 and ABOVE
[not found] <003501c1dfc2$c1f28330$010b10ac@sbp.uptime.at>
@ 2002-04-09 12:56 ` Oliver Pitzeier
2002-04-09 13:46 ` Stephen C. Tweedie
0 siblings, 1 reply; 4+ messages in thread
From: Oliver Pitzeier @ 2002-04-09 12:56 UTC (permalink / raw)
To: axp-kernel-list; +Cc: linux-kernel
OK... I now run kernel 2.4.18 on my alpha with ext3.
I wanted to delete /usr/src/linux, because I want to recompile it again
with another kernel...
That's what I get. I really do not understand it anymore!
I could cry! OK, I have already done it. :o)
[root@node1 src]# rm -Rf linux
rm: cannot stat `linux/fs/hpfs': Input/output error
rm: cannot change to directory `linux/fs/fat': Not a directory
rm: cannot stat `linux/fs/autofs': Input/output error
rm: cannot stat `linux/fs/efs': Input/output error
rm: cannot stat `linux/fs/partitions': Input/output error
rm: cannot stat `linux/fs/autofs4': Input/output error
rm: cannot stat `linux/fs/ext3': Input/output error
rm: cannot remove directory `linux/fs': Directory not empty
rm: cannot stat `linux/lib': Input/output error
rm: cannot stat `linux/include/asm-generic': Input/output error
rm: cannot change to directory `linux/include/asm-mips/baget': Not a
directory
rm: cannot stat `linux/include/asm-mips/ddb5xxx': Input/output error
rm: cannot stat `linux/include/asm-mips/mips-boards': Input/output error
rm: cannot remove directory `linux/include/asm-mips': Directory not
empty
rm: cannot stat `linux/include/scsi': Input/output error
rm: cannot change to directory `linux/include/asm-arm/arch-nexuspci':
Not a directory
rm: cannot stat `linux/include/asm-arm/arch-ebsa285': Input/output error
rm: cannot stat `linux/include/asm-arm/arch-shark': Input/output error
rm: cannot change to directory `linux/include/asm-arm/arch-l7200': Not a
directory
rm: cannot stat `linux/include/asm-arm/arch-anakin': Input/output error
rm: cannot remove directory `linux/include/asm-arm': Directory not empty
rm: cannot stat `linux/include/video': Input/output error
rm: cannot stat `linux/include/pcmcia': Input/output error
rm: cannot stat `linux/include/asm-ia64/sn': Input/output error
rm: cannot remove directory `linux/include/asm-ia64': Directory not
empty
rm: cannot change to directory `linux/include/asm-mips64': Not a
directory
rm: cannot stat `linux/include/config/blk/dev/ataraid': Input/output
error
rm: cannot stat `linux/include/config/blk/dev/3w/xxxx': Input/output
error
rm: cannot remove directory `linux/include/config/blk/dev/3w': Directory
not empty
rm: cannot remove directory `linux/include/config/blk/dev': Directory
not empty
rm: cannot remove directory EXT3-fs error (device sd(8,18)):
ext3_free_blocks: bit already cleared for block 1607322
`linux/include/cEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607323
onfig/blk': DireEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607324
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607325
rm: cannot statEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607326
`linux/include/EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607327
config/ip/nf': IEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607328
nput/output erroEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607329
r
rm: cannot reEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607330
move directory `EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607331
linux/include/coEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607332
nfig/ip': DirectEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607333
ory not empty
rEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607334
m: cannot stat `EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607335
linux/include/coEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607337
nfig/idedma/pci'EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607338
: Input/output eEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607339
rror
rm: cannotEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already
cleared for block 1607340
remove directorEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607341
y `linux/includeEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607336
/config/idedma':EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607342
Directory not eEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607343
mpty
rm: cannotEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already
cleared for block 1607344
stat `linux/incEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607345
lude/config/scsiEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607346
/ncr53c8xx': InpEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607347
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607348
rm: cannot remoEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607349
ve directory `liEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607350
nux/include/confEXT3-fs error (device sd(8,18)): ext3_free_inode: bit
already cleared for inode 800146
ig/scsi': DirectEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607351
ory not empty
rEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607352
m: cannot stat `EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607353
linux/include/coEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607354
nfig/elmc': InpuEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607355
t/output error
rm: cannot stat EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607356
`linux/include/cEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607357
onfig/8139': InpEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607358
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607359
rm: cannot statEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607360
`linux/include/EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607361
config/dl2k': InEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607362
put/output errorEXT3-fs error (device sd(8,18)): ext3_free_inode: bit
already cleared for inode 800149
rm: cannot chaEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607363
nge to directoryEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607364
`linux/include/EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607365
config/myri': NoEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607366
t a directory
rEXT3-fs error (device sd(8,18)): ext3_free_inode: bit already cleared
for inode 800150
m: cannot stat `EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607367
linux/include/coEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607368
nfig/pc110': InpEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607369
EXT3-fs error (device sd(8,18)): ext3_free_inode: bit already cleared
for inode 800151
rm: cannot stat `linux/include/EXT3-fs error (device sd(8,18)):
ext3_free_blocks: bit already cleared for block 1607370
config/input': IEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
already cleared for block 1607371
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607372
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607373
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607374
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607375
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607376
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607377
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607378
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607379
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607380
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607381
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607383
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607384
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607385
EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit already cleared
for block 1607382
EXT3-fs error (device sd(8,18)): ext3_free_inode: bit already cleared
for inode 800152
> -----Original Message-----
> From: axp-kernel-list-admin@redhat.com
> [mailto:axp-kernel-list-admin@redhat.com] On Behalf Of Oliver Pitzeier
> Sent: Tuesday, April 09, 2002 2:34 PM
> To: axp-kernel-list@redhat.com
> Subject: RE: Kernel 2.4.9 and ABOVE
>
>
> > And you don't get these FS errors when using other kernels?
> > Does the system freeze up or continue as if nothing had
> > happened? File corruption? Disk continously thrashing?
>
> it works perfektly as if nothing has happened.
> with other kernels i don't get such errors...
>
> > How old are the disk[s] that you have as it could (my guess)
> > be failing disks, because I believe I have seen something
> > like it when the communication between disk and controller
> > became troublesome, ie. a bad disk.
>
> the machines are very new and the disk also. the disk are
> not older than a half year...
>
> > Else, I have no idea of what it could be?
>
> me too! :o)
>
> however... i go on...
>
> -Oliver
>
>
>
>
> _______________________________________________
> Axp-kernel-list mailing list
> Axp-kernel-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/ax> p-kernel-list
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Kernel 2.4.9 and ABOVE
@ 2002-04-09 13:04 Oliver Pitzeier
0 siblings, 0 replies; 4+ messages in thread
From: Oliver Pitzeier @ 2002-04-09 13:04 UTC (permalink / raw)
To: o.pitzeier, axp-kernel-list; +Cc: linux-kernel
after rebooting i can delete the directory...
i really do not understand it any more. :o)
> -----Original Message-----
> From: Oliver Pitzeier [mailto:o.pitzeier@uptime.at]
> Sent: Tuesday, April 09, 2002 2:56 PM
> To: 'axp-kernel-list@redhat.com'
> Cc: 'linux-kernel@vger.kernel.org'
> Subject: RE: Kernel 2.4.9 and ABOVE
>
>
> OK... I now run kernel 2.4.18 on my alpha with ext3.
>
> I wanted to delete /usr/src/linux, because I want to
> recompile it again with another kernel...
>
> That's what I get. I really do not understand it anymore!
> I could cry! OK, I have already done it. :o)
>
> [root@node1 src]# rm -Rf linux
> rm: cannot stat `linux/fs/hpfs': Input/output error
> rm: cannot change to directory `linux/fs/fat': Not a directory
> rm: cannot stat `linux/fs/autofs': Input/output error
> rm: cannot stat `linux/fs/efs': Input/output error
> rm: cannot stat `linux/fs/partitions': Input/output error
> rm: cannot stat `linux/fs/autofs4': Input/output error
> rm: cannot stat `linux/fs/ext3': Input/output error
> rm: cannot remove directory `linux/fs': Directory not empty
> rm: cannot stat `linux/lib': Input/output error
> rm: cannot stat `linux/include/asm-generic': Input/output error
> rm: cannot change to directory
> `linux/include/asm-mips/baget': Not a directory
> rm: cannot stat `linux/include/asm-mips/ddb5xxx': Input/output error
> rm: cannot stat `linux/include/asm-mips/mips-boards':
> Input/output error
> rm: cannot remove directory `linux/include/asm-mips':
> Directory not empty
> rm: cannot stat `linux/include/scsi': Input/output error
> rm: cannot change to directory
> `linux/include/asm-arm/arch-nexuspci': Not a directory
> rm: cannot stat `linux/include/asm-arm/arch-ebsa285':
> Input/output error
> rm: cannot stat `linux/include/asm-arm/arch-shark': Input/output error
> rm: cannot change to directory
> `linux/include/asm-arm/arch-l7200': Not a directory
> rm: cannot stat `linux/include/asm-arm/arch-anakin':
> Input/output error
> rm: cannot remove directory `linux/include/asm-arm':
> Directory not empty
> rm: cannot stat `linux/include/video': Input/output error
> rm: cannot stat `linux/include/pcmcia': Input/output error
> rm: cannot stat `linux/include/asm-ia64/sn': Input/output error
> rm: cannot remove directory `linux/include/asm-ia64':
> Directory not empty
> rm: cannot change to directory `linux/include/asm-mips64':
> Not a directory
> rm: cannot stat `linux/include/config/blk/dev/ataraid':
> Input/output error
> rm: cannot stat `linux/include/config/blk/dev/3w/xxxx':
> Input/output error
> rm: cannot remove directory
> `linux/include/config/blk/dev/3w': Directory not empty
> rm: cannot remove directory `linux/include/config/blk/dev':
> Directory not empty
> rm: cannot remove directory EXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607322
> `linux/include/cEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607323
> onfig/blk': DireEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607324
> EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
> already cleared for block 1607325
>
> rm: cannot statEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607326
> `linux/include/EXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607327
> config/ip/nf': IEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607328
> nput/output erroEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607329 r
> rm: cannot reEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607330 move
> directory `EXT3-fs error (device sd(8,18)): ext3_free_blocks:
> bit already cleared for block 1607331 linux/include/coEXT3-fs
> error (device sd(8,18)): ext3_free_blocks: bit already
> cleared for block 1607332
> nfig/ip': DirectEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607333 ory
> not empty rEXT3-fs error (device sd(8,18)): ext3_free_blocks:
> bit already cleared for block 1607334
> m: cannot stat `EXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607335
> linux/include/coEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607337
> nfig/idedma/pci'EXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607338
> : Input/output eEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607339 rror
> rm: cannotEXT3-fs error (device sd(8,18)): ext3_free_blocks:
> bit already cleared for block 1607340 remove directorEXT3-fs
> error (device sd(8,18)): ext3_free_blocks: bit already
> cleared for block 1607341 y `linux/includeEXT3-fs error
> (device sd(8,18)): ext3_free_blocks: bit already cleared for
> block 1607336 /config/idedma':EXT3-fs error (device
> sd(8,18)): ext3_free_blocks: bit already cleared for block
> 1607342 Directory not eEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607343 mpty
> rm: cannotEXT3-fs error (device sd(8,18)): ext3_free_blocks:
> bit already cleared for block 1607344 stat `linux/incEXT3-fs
> error (device sd(8,18)): ext3_free_blocks: bit already
> cleared for block 1607345 lude/config/scsiEXT3-fs error
> (device sd(8,18)): ext3_free_blocks: bit already cleared for
> block 1607346
> /ncr53c8xx': InpEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607347
> EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
> already cleared for block 1607348
>
> rm: cannot remoEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607349 ve
> directory `liEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607350
> nux/include/confEXT3-fs error (device sd(8,18)):
> ext3_free_inode: bit already cleared for inode 800146
> ig/scsi': DirectEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607351 ory
> not empty rEXT3-fs error (device sd(8,18)): ext3_free_blocks:
> bit already cleared for block 1607352
> m: cannot stat `EXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607353
> linux/include/coEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607354
> nfig/elmc': InpuEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607355 t/output error
> rm: cannot stat EXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607356
> `linux/include/cEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607357
> onfig/8139': InpEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607358
> EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
> already cleared for block 1607359
>
> rm: cannot statEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607360
> `linux/include/EXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607361
> config/dl2k': InEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607362
> put/output errorEXT3-fs error (device sd(8,18)):
> ext3_free_inode: bit already cleared for inode 800149
>
> rm: cannot chaEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607363 nge
> to directoryEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607364
> `linux/include/EXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607365
> config/myri': NoEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607366 t a
> directory rEXT3-fs error (device sd(8,18)): ext3_free_inode:
> bit already cleared for inode 800150
> m: cannot stat `EXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607367
> linux/include/coEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607368
> nfig/pc110': InpEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607369
> EXT3-fs error (device sd(8,18)): ext3_free_inode: bit already
> cleared for inode 800151
>
> rm: cannot stat `linux/include/EXT3-fs error (device
> sd(8,18)): ext3_free_blocks: bit already cleared for block 1607370
> config/input': IEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607371
> EXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
> already cleared for block 1607372 EXT3-fs error (device
> sd(8,18)): ext3_free_blocks: bit already cleared for block
> 1607373 EXT3-fs error (device sd(8,18)): ext3_free_blocks:
> bit already cleared for block 1607374 EXT3-fs error (device
> sd(8,18)): ext3_free_blocks: bit already cleared for block
> 1607375 EXT3-fs error (device sd(8,18)): ext3_free_blocks:
> bit already cleared for block 1607376 EXT3-fs error (device
> sd(8,18)): ext3_free_blocks: bit already cleared for block
> 1607377 EXT3-fs error (device sd(8,18)): ext3_free_blocks:
> bit already cleared for block 1607378 EXT3-fs error (device
> sd(8,18)): ext3_free_blocks: bit already cleared for block
> 1607379 EXT3-fs error (device sd(8,18)): ext3_free_blocks:
> bit already cleared for block 1607380 EXT3-fs error (device
> sd(8,18)): ext3_free_blocks: bit already cleared for block
> 1607381 EXT3-fs error (device sd(8,18)): ext3_free_blocks:
> bit already cleared for block 1607383 EXT3-fs error (device
> sd(8,18)): ext3_free_blocks: bit already cleared for block
> 1607384 EXT3-fs error (device sd(8,18)): ext3_free_blocks:
> bit already cleared for block 1607385 EXT3-fs error (device
> sd(8,18)): ext3_free_blocks: bit already cleared for block
> 1607382 EXT3-fs error (device sd(8,18)): ext3_free_inode: bit
> already cleared for inode 800152
>
> > -----Original Message-----
> > From: axp-kernel-list-admin@redhat.com
> > [mailto:axp-kernel-list-admin@redhat.com] On Behalf Of
> Oliver Pitzeier
> > Sent: Tuesday, April 09, 2002 2:34 PM
> > To: axp-kernel-list@redhat.com
> > Subject: RE: Kernel 2.4.9 and ABOVE
> >
> >
> > > And you don't get these FS errors when using other
> kernels? Does the
> > > system freeze up or continue as if nothing had happened? File
> > > corruption? Disk continously thrashing?
> >
> > it works perfektly as if nothing has happened.
> > with other kernels i don't get such errors...
> >
> > > How old are the disk[s] that you have as it could (my guess) be
> > > failing disks, because I believe I have seen something
> like it when
> > > the communication between disk and controller became troublesome,
> > > ie. a bad disk.
> >
> > the machines are very new and the disk also. the disk are
> > not older than a half year...
> >
> > > Else, I have no idea of what it could be?
> >
> > me too! :o)
> >
> > however... i go on...
> >
> > -Oliver
> >
> >
> >
> >
> > _______________________________________________
> > Axp-kernel-list mailing list
> > Axp-kernel-list@redhat.com
> > https://listman.redhat.com/mailman/listinfo/ax> p-kernel-list
> >
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Kernel 2.4.9 and ABOVE
2002-04-09 12:56 ` Kernel 2.4.9 and ABOVE Oliver Pitzeier
@ 2002-04-09 13:46 ` Stephen C. Tweedie
2002-04-10 8:23 ` Oliver Pitzeier
0 siblings, 1 reply; 4+ messages in thread
From: Stephen C. Tweedie @ 2002-04-09 13:46 UTC (permalink / raw)
To: axp-kernel-list; +Cc: linux-kernel
Hi,
On Tue, Apr 09, 2002 at 02:56:17PM +0200, Oliver Pitzeier wrote:
> rm: cannot remove directory EXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit already cleared for block 1607322
> `linux/include/cEXT3-fs error (device sd(8,18)): ext3_free_blocks: bit
> already cleared for block 1607323
Is this captured console output or actual syslog contents? Depending
on the log level, it's quite possible that there are kernel messages
which are going to one source or the other but not both.
--Stephen
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Kernel 2.4.9 and ABOVE
2002-04-09 13:46 ` Stephen C. Tweedie
@ 2002-04-10 8:23 ` Oliver Pitzeier
0 siblings, 0 replies; 4+ messages in thread
From: Oliver Pitzeier @ 2002-04-10 8:23 UTC (permalink / raw)
To: axp-kernel-list; +Cc: linux-kernel, aleks
OK I got it... My Alpha works now.
I must have been an idiot. :o)
One of the harddrives seems to have errors. After reinstalling
RedHat on the other drive. tune2fs -j -c0 -i0 /dev/sda[1,3,4,5]
Editing fstab, rebooting.
Crashing the system via the halt button. Restarting -> System
recovers the journal and then YIPIEEE(!) no more errors.
Everything works!
Thanks to everyone who helped me with this f***in' problem.
Especially to Stephen Tweedie, Jochen Buehler and
Peter Leif Rasmussen...
-Oliver
PS: I'm now running kernel 2.4.18-grsec-1.9.4 :o)
PPS: I guess it's now up to RedHat to build a nice Kernel-RPMs
and release (together with Compaq) RedHat 7.2 Alpha Edition. :o)
> -----Original Message-----
> From: axp-kernel-list-admin@redhat.com
> [mailto:axp-kernel-list-admin@redhat.com] On Behalf Of
> Stephen C. Tweedie
> Sent: Tuesday, April 09, 2002 3:47 PM
> To: axp-kernel-list@redhat.com
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: Kernel 2.4.9 and ABOVE
>
>
> Hi,
>
> On Tue, Apr 09, 2002 at 02:56:17PM +0200, Oliver Pitzeier wrote:
>
> > rm: cannot remove directory EXT3-fs error (device sd(8,18)):
> > ext3_free_blocks: bit already cleared for block 1607322
> > `linux/include/cEXT3-fs error (device sd(8,18)):
> ext3_free_blocks: bit
> > already cleared for block 1607323
>
> Is this captured console output or actual syslog contents?
> Depending on the log level, it's quite possible that there
> are kernel messages which are going to one source or the
> other but not both.
>
> --Stephen
>
>
>
> _______________________________________________
> Axp-kernel-list mailing list
> Axp-kernel-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/ax> p-kernel-list
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2002-04-10 8:24 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <003501c1dfc2$c1f28330$010b10ac@sbp.uptime.at>
2002-04-09 12:56 ` Kernel 2.4.9 and ABOVE Oliver Pitzeier
2002-04-09 13:46 ` Stephen C. Tweedie
2002-04-10 8:23 ` Oliver Pitzeier
2002-04-09 13:04 Oliver Pitzeier
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox