Re: [qubes-users] Btrfs (file-reflink): Why is the CoW on a volatile.img enabled?

2023-03-04 Thread 449f09c92
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

Re: [qubes-users] Btrfs (file-reflink): Why is the CoW on a volatile.img enabled?

2023-03-04 Thread Rusty Bird
-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)

Re: [qubes-users] Btrfs (file-reflink): Why is the CoW on a volatile.img enabled?

2023-03-04 Thread Rusty Bird
-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