https://bugzilla.kernel.org/show_bug.cgi?id=14830 --- Comment #35 from Michael Godfrey <godfrey@xxxxxxxxxxxxxxxx> 2010-04-20 03:46:28 --- Dave (above) said: "Sync is acting as designed right now. I agree it's not ideal, but it's now defaulting to slow-but-safe behaviour rather than the previous behaviour of potentially not syncing everything that was dirty at the time of the sync call. Dave," 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. Take a look at the reports above which show nfsd being effectively blocked for periods of more than 20 minutes. For me this is not just "not ideal" but simply useless. I do not see how a system with this behavior can be used. I also do not see why sync completing with dirty data is a problem. In an active system there will be new dirty data within milliseconds of sync completion no matter what it does. I am well-aware that this is not a simple problem. But, a solution that is consistent with the usability of the system is necessary. Michael -- 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
