Comment 36 for bug 204133

Colin, that is fantastic, I think we should try to have it in hardy.proposed as this is a clear improvement over the sysctl hack and should better address data loss situations in hard reboot scenarios.

One question: I can certainly appreciate the value of quick syncs for the host filesystem (2), but why do we exactly need -o loop,sync in the nested filesystem? Is there any benefit for that? My understanding is that if the host flushes quickly, the nested journal should be safe, whether the nested fs syncs quickly or not.