If right after starting the snapshot creation ioctl we perform a write against a
file followed by a truncate, with both operations increasing the file's size, we
can get a snapshot tree that reflects a state of the source subvolume's tree
where
the file truncation happened but the write operation
On Wed, 29 Oct 2014 08:21:12 +, Filipe Manana wrote:
If right after starting the snapshot creation ioctl we perform a write
against a
file followed by a truncate, with both operations increasing the file's size,
we
can get a snapshot tree that reflects a state of the source subvolume's