On 26/06/2019 05.19, Manuel Amador (Rudd-O) wrote:
>
> Folks,
>
> I haven't been able to understand the codebase for the "file" storage
> pool very well.
>
> At which point in the lifetime of a VM do changes get merged down from
> the COW private.img to the base private img?
>
> If my machine crashes, what prevents the data in the COW private.img
> from being lost next time the VM starts?
>
> Thanks.
>
For the record, I did understand the equivalent code in the "reflink"
pool (around which I'm modeling my ZFS pool code) -- the stop() method
moves the COW file to the base file, and the start() method copies the
base file to the COW file EXCEPT when there is already a COW file in
place, in which case it simply does nothing (thereby ensuring that the
COW file, with changes yet to be committed before the crash, is not lost).
--
Rudd-O
http://rudd-o.com/
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-devel+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-devel/bc2258e1-6726-a419-34eb-0d8df9ba707f%40rudd-o.com.
For more options, visit https://groups.google.com/d/optout.
