Re: 2.6.18-mm2: ext3 BUG?

On Thu, 5 Oct 2006, Andrew Morton wrote:

> Don't know.  The usual diagnosis for this sort of thing is "your disk 
> shat itself".  Could be a bad disk, bad power supply, bad memory, some 
> piece of kernel code went and trashed some memory, bug in the driver.  
> It's a mystery, sorry.

Actually I have also experienced some ext3 corruption (*) on my virtual 
machine under qemu emulation with 2.6.18-mm3, but I thought my previous 
other "strange" activities were guilty. Now it seems that there could be 
indeed something rotten in ext3 driver. Will try to reproduce, and if I am 
able to do so, I will bisect.

(*) Similar symptoms to the original poster - just fsck finding a few 
orphaned entries and lost blocks, etc.

-- 
Jiri Kosina