Jamie Lokier wrote:
But assuming it stays shared until you modify the actual data, could
the documentation make this important fact a bit more prominent:
Opening a file, reading it, read-only or private mappings, and
simple attribute updates (chown, chmod, futimes, as well as
automatic atime updates) will not trigger copy-on-write and will
not return ENOSPC errors.
almost... more like:
automatic atime updates) will not trigger file data copy-on-write
and will not return ENOSPC errors unless the filesytem would have
returned ENOSPC if the file had no reflink.
filesystems such as btrfs that COW metadata changes can
generate ENOSPC on any attribute update!
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
