On Thu 02-04-09 22:24:29, Nick Piggin wrote: > On Thursday 02 April 2009 09:36:13 Ying Han wrote: > > Hi Jan: > > I feel that the problem you saw is kind of differnt than mine. As > > you mentioned that you saw the PageError() message, which i don't see > > it on my system. I tried you patch(based on 2.6.21) on my system and > > it runs ok for 2 days, Still, since i don't see the same error message > > as you saw, i am not convineced this is the root cause at least for > > our problem. I am still looking into it. > > So, are you seeing the PageError() every time the problem happened? > > So I asked if you could test with my workaround of taking truncate_mutex > at the start of ext2_get_blocks, and report back. I never heard of any > response after that. > > To reiterate: I was able to reproduce a problem with ext2 (I was testing > on brd to get IO rates high enough to reproduce it quite frequently). > I think I narrowed the problem down to block allocation or inode block > tree corruption because I was unable to reproduce it with that hack in > place. Nick, what load did you use for reproduction? I'll try to reproduce it here so that I can debug ext2... Honza -- Jan Kara <jack@xxxxxxx> SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
