Re: Bad Drive or JFS bug? (2.4.25-pre8)

[Dave Kleikamp]

On Wed, 2004-02-11 at 10:49, Kevin Fenzi wrote:
> Greetings. 
> 
> It's unclear to me if this is a jfs error, or if my drive is simply
> dying. There are no other indications of errors with the drive, but in
> the logs: 

JFS definitely ran into some corrupt metadata.  It could either be
corrupt on disk, or a memory-corruption problem.  I don't know if
hardware is the cause, but you say that nothing indicates that.  If it
is caused by a software bug, it would be hard to track down unless it is
repeatable.  The BUG() itself should probably be replaced by something
nicer, like the first two errors reported by dbFree.

At this point the superblock should be marked dirty, so fsck should
attempt to repair the damage upon reboot.  I'd like to know if you
continue to see problems.

Thanks,
Shaggy
> 
> Feb 11 04:04:59 voldemort kernel: blkno = 6d2e74726f, nblocks = 65646c
> Feb 11 04:04:59 voldemort kernel: ERROR: (device ide0(3,3)): dbFree: block to be freed is outside the map
> Feb 11 04:04:59 voldemort kernel: blkno = 3000003831, nblocks = 392e6d
> Feb 11 04:04:59 voldemort kernel: ERROR: (device ide0(3,3)): dbFree: block to be freed is outside the map
> Feb 11 04:04:59 voldemort kernel: BUG at jfs_dmap.c:2764 assert(newval == leaf[buddy])
> Feb 11 04:04:59 voldemort kernel: kernel BUG at jfs_dmap.c:2764!

-- 
David Kleikamp
IBM Linux Technology Center

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/