On Monday 24 June 2002 10:26 am, Stephen Tweedie wrote: > Hi, > > On Sat, Jun 22, 2002 at 04:18:39PM -0400, Daniel Andor <Daniel.Andor@physics.org> wrote: > > > When trying to run a particular program, I reproducibly get a few > > > dozen kernel messages of the form: > > > > > > attempt to access beyond end of device > > > 03:06: rw=0, want=536995844, limit=11680168 > > > attempt to access beyond end of device > > > 03:06: rw=0, want=1342296068, limit=11680168 > > > > EXT3-fs error (device ide0(3,6)): ext3_free_blocks: Freeing blocks not in > > datazone - block = 788558848, count = 1 Kernel panic: EXT3-fs panic > > (device ide0(3,6)): load_block_bitmap: block_group >= groups_count - > > block_group = 131071, groups_count = 90 > > What kernel? What sort of hardware? Are there any other log > messages? This could easily be a sign of random data corruption > hitting disk, for example --- it's a vague problem description so far, > so any extra detail you can provide would help. Sorry, yes, more info would help: Linux 2.4.17-pre8, Thinkpad X21 20GB IDE harddisk No other error messages at all as far as I can see. > > I've tried fsck when the systemm is ro, but it doesn't make any > > difference. > > Did fsck find any errors? What do you mean when you say it makes no > difference --- exactly the same problem occurs again later, or is the > next problem similar but slightly different in detail? As far as I can tell, the problem remains the same, with identical error messages. I can reproduce the error by running the same program. Fsck returns: fsck 1.25 (20-Sep-2001) e2fsck 1.25 (20-Sep-2001) /dev/hda6: recovering journal Clearing orphaned inode 230513 (uid=0, gid=0, mode=020600, size=0) Clearing orphaned inode 227179 (uid=0, gid=0, mode=020600, size=0) /dev/hda6: clean, 275580/1460160 files, 2728422/2920042 blocks Thanks, Daniel.
