On Sun, 3 Sep 2000, Mohammad A. Haque wrote:
> Ok, looking better. I havent been able to forcibly corrupt my mailboxes
> like I did before. Yet anyways. I left my machine for about 10 mins and
> came back and noticed this...
>
> Sep 3 16:46:29 viper kernel: attempt to access beyond end of device
> Sep 3 16:46:29 viper kernel: 21:01: rw=0, want=1070936764,
> limit=30015184
Most likely screwed indirect blocks with pointers _way_ off-base. Or
direct pointers, for that matter.
> Sep 3 16:46:29 viper kernel: attempt to access beyond end of device
> Sep 3 16:46:29 viper kernel: 21:01: rw=0, want=1422438616,
> limit=30015184
> ........
>
> Of course I can't tell what drive it was trying to access or anything.
hde1, apparently (0x21:0x01)
> Later, I was deleting all the erraneous dead mailboxes I made from
> testing before and I got this....
>
> Sep 3 16:48:03 viper kernel: EXT2-fs error (device
> ide2(33,1)): ext2_free_blocks: Freeing blocks not in datazone - block =
> 826250760, count = 1
> Sep 3 16:48:03 viper kernel: EXT2-fs error (device
> ide2(33,1)): ext2_free_blocks: Freeing blocks not in datazone - block =
> 3904384768, count = 1
> Sep 3 16:48:03 viper kernel: EXT2-fs error (device
> ide2(33,1)): ext2_free_blocks: Freeing blocks not in datazone - block =
> 160208392, count = 1
> Sep 3 16:48:03 viper kernel: EXT2-fs error (device
> ide2(33,1)): ext2_free_blocks: Freeing blocks not in datazone - block =
> 807171584, count = 1
> .....
>
> Hope this stuff help track down the problem. I'm really glad 2.4 hasn't
> been released yet. This would have been a killer.
This might be a result of prior corruption - try to do forced fsck and
reproduce the problems with new kernel after repairs are done.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
