Jamie Lokier wrote:
Writing in place or new-place on a *non-shared* (i.e. non-snapshotted) file is the choice which is useful. It's a filesystem implementation detail, not a semantic difference. I'm suggesting writing in place may do no harm and be more like the expected behaviour with programs that use O_DIRECT, which are usually databases. How about a btrfs mount option? in_place_write=never/always/direct_only. (Default direct_only).
The harm is creating a special guarantee for just one case of "don't move my data" based on a transient file open mode. What about defragmenting or moving the extent to another device for performance or for (failing) device removal? We are on a slippery slope for presumed expectations. jim -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
