Re: [qubes-users] Btrfs (file-reflink): Why is the CoW on a volatile.img enabled?
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 qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/978266fe-07db-32a1-ba3f-23552919b298%40cock.li.
[qubes-users] Btrfs (file-reflink): Why is the CoW on a volatile.img enabled?
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 used as swap? Just curious. -- 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 qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/db2302d3-8a9b-3dd8-4b3f-96ba31e065c4%40cock.li.