Thank you for your clarification.
Also, many thanks for maintaining the file-reflink storage driver.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Rusty Bird:
> Disabling CoW and hence checksums (besides being specific to Btrfs -
> file-reflink is filesystem agnostic)
Although for volatile volumes in particular it might be possible to
get away with (optionally, configured per-volume)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
449f09c92:
> had to edit the relevant code to disable CoW when volatile.img is
> created
file-reflink doesn't inherently do CoW for volatile volumes, it just
defaults to whatever the underlying location on the filesystem does.
For Btrfs, to get
I have /dev/xvdc configured as a 10GB swap and had to edit the relevant
code to disable CoW when volatile.img is created to avoid overloading
dom0 by checksum calculation when swapping out occurs in the VM.
Is there any reason why copy-on-write is enabled on volatile volumes
that are mostly
