Comment 44 for bug 204133

Martin, I am not sure what you are referring to as the "linux" bug, there a few related kernel issues I am aware of:

1) The "linux" bug mentioned in comment #17 is relevant for low levels of dirty_ratio. The ntfs-3g patch will avoid lowering the dirty_ratio and will indirectly help (which is a subcase of #2 above).

2) There was some discussion on the performance / reliability of the loop device in write intensive set-ups. See for instance http://lkml.org/lkml/2008/1/9/50. Colin seems to like the dm-loop approach. I am not sure if there are data loss scenarios that could be improved upon by using dm-loop or whether it is mostly a performance issue. My guess is that dm-loop might help with point #1 in comment #31

3) It would be nice to be able to use the standard mount option name "-o sync" as opposed to have to create a new one for each filesystem "-o syncio". Not least because it will create a bit of special casing in other code (lupin/initramfs-tools). From a past discussion with Colin it emerged that the naming was to work around fuse -o sync handling.

4) There is also a remount issue with loopdevices (see #201750). On top of that, there are separate remount issues for ntfs-3g (see #186117), even worse, it seems that remounting ntfs-3g ro/rw can produce data loss (https://bugs.edge.launchpad.net/wubi/+bug/186117/comments/10). Not sure if newer versions of fuse/ntfs-3g address this.

5) Related to the above there are the shutdown issues mentioned by Colin in comment #19. I am not sure what is that state of that given A) the ntfs-3g patch and possibly B) dm-loop usage.