https://bugzilla.kernel.org/show_bug.cgi?id=14830 Ritesh Raj Sarraf <rrs@xxxxxxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rrs@xxxxxxxxxxxxxx --- Comment #36 from Dave Chinner <david@xxxxxxxxxxxxx> 2010-04-20 05:24:39 --- (In reply to comment #35) > Are you aware that this blocks other IO so that a user who requests > a read of some data may have to wait for something like 20 minutes > before getting a response? This includes, for instance, just typing > vi xxx. That's not a just a read - vi(m) writes a backup file when you open it. So it's blocking on writes. However, that sort of antisocial behaviour under heavy write loads is usually caused by a filesystem concurrency limitation or a IO scheduler problem, not sync. However, unless you can reproduce the read hangs on XFS when sync is running, then I'm not the expert you're looking for to debug them. ;) But I do know the endless sync problem is filesystem independent and I'm trying to do something about mitigating it's effects: http://lkml.org/lkml/2010/4/19/410 > Take a look at the reports above which show nfsd being effectively > blocked for periods of more than 20 minutes. Can't say I've heard of any such recent problems on XFS.... Cheers, Dave. --- Comment #37 from Neil Broomfield <neil.broomfield@xxxxxxxxxxxxx> 2010-04-20 09:00:28 --- "Can't say I've heard of any such recent problems on XFS...." Are these not effectivly the same issue?: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/276476 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/494476 Neil -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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
