If you're not using upspinserver-gcp you can stop reading now.
We just
committed a fix for a significant bug in Upspin's abstraction layer for talking to Google Cloud Storage. The bug was that, under certain conditions, an object could be reported as successfully written to cloud storage, but its contents would be empty.
Users of upspinserver-gcp should update to the latest version:
Build it for the target os/architecture (linux/amd64 in this example):
And then re-deploy it to your server (stop the service, copy the upspinserver binary, run
setcap if necessary, and start the service again).
To verify that all your data is intact you can just read it, as checksums are validated on read.
One simple way to read all the data in an Upspin tree is to use the 'upspin tar' command':
Apologies for the inconvenience.
Andrew