[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: ext3 Problem in 2.4.20-ac1?



Hi,

On Thu, 2002-12-05 at 15:35, Ralf Hildebrandt wrote:

> Since I ain't got a better place to report this, I do it here:
> Kernel 2.4.20-ac1
> 
> Dec  5 00:00:07 postamt1 httpd: httpd startup succeeded
> Dec  5 15:48:35 postamt1 kernel: swap_dup: Bad swap file entry 516a444c
> Dec  5 15:48:36 postamt1 kernel: swap_dup: Bad swap file entry 7741314a
> Dec  5 15:48:36 postamt1 kernel: EIP:    0010:[__free_pages_ok+94/800] Not tainted

This is a pure VM oops.  There's no sign of ext3 involvement here.

> Dec  5 15:53:53 postamt1 kernel:  <2>EXT3-fs error (device sd(8,6)): ext3_free_blocks: Freeing blocks not in datazone - block = 1094928743, count = 1
> Dec  5 15:53:53 postamt1 kernel: EXT3-fs error (device sd(8,6)): ext3_free_blocks: Freeing blocks not in datazone - block = 1095059815, count = 1
> Dec  5 15:53:53 postamt1 kernel: EXT3-fs error (device sd(8,6)): ext3_free_blocks: Freeing blocks not in datazone - block = 1094996087, count = 1
> Dec  5 15:53:53 postamt1 kernel: EXT3-fs error (device sd(8,6)): ext3_free_blocks: Freeing blocks not in datazone - block = 1380209241, count = 1
> Dec  5 15:53:53 postamt1 kernel: EXT3-fs error (device sd(8,6)): ext3_free_blocks: Freeing blocks not in datazone - block = 1095060801, count = 1

Ext3 is then complaining that some of its indirect blocks look corrupt. 
This looks more like a VM or (more likely) hardware problem to me.

> * ext3 or VM problem?

Hardware is my first guess.

> * How to track down more professionally?

Run memtest86.

> * fsck recommended?

In this sort of situation, always.

> * Should I report this to lkml?

Check the hardware as best you can.  Then, either lkml or
linux-mm kvack org, unless you get a better oops which points more
clearly towards an ext3 problem.

Cheers, 
 Stephen





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]