Hey Jason,

The *main* thing I'm concerned about, though, is that the disk for one
of my large VMs appears to have been truncated -- it's virtual size is
300GB, I think the actual size was probably just under half of that,
but it's actual size is now reported to be less than a gig, and it's
taking up only 300MB of space. I'm afraid the answer is no, but I'm
hoping that the data might be recoverable from somewhere on the
bricks...

glusterfs is using features.shard with 4MB shards, so it is natural to see a VM disk as 300GB virtual size with a very small actual size, as the rest of the data is in the shards.

The best way to check the VM is to power it off and power it on.

I am wondering how you managed to upgrade as vdsm-gluster and glusterfs-gnfs (depend each other) have a dependency issues in 4.3 repo ?!?

Best Regards,
Strahil Nikolov