On Fri, Mar 13, 2009 at 06:06:07PM +0100, ext Jorge Boncompte [DTI2] wrote:> Nick Piggin escribió:> > On Tue, Mar 10, 2009 at 05:49:13PM +0100, Jorge Boncompte [DTI2] wrote:> >> Nick Piggin escribió:> >>> Ah, of course, it would be due to directory-in-pagecache. You need> >>> the following patch if you expect this to work.> >>>> >>> And that confirms the ext3 problem is a different one because it> >>> doesn't use directory in pagecache I think. Well, I'll look at> >>> that one tomorrow.> Hi Nick, no problems noticed in the last days running with the below > patch...> > --- linux-2.6.29-rc8/fs/super.c 2009-03-13 13:46:19 +0100> +++ kernel/fs/super.c 2009-03-13 13:47:50 +0100> @@ -647,6 +647,8 @@ int do_remount_sb(struct super_block *sb> acct_auto_close(sb);> shrink_dcache_sb(sb);> fsync_super(sb);> + if (sb->s_bdev && (flags & MS_RDONLY))> + invalidate_bdev(sb->s_bdev);> > /* If we are remounting RDONLY and current sb is read/write,> make sure there are no rw files opened */>

Hello,

first off, sorry if you getting this email twice.

I also tried to do ext3/ext4 fs smoketesting and used Adraian'sscript. I am consistently getting the same results - filesystem get'scorrupted. I tested on quad Xeon, with patches posted in this thread.