0

I'm about to evaluate gcsfuse for use in a system with a database daemon. The daemon is peculiar. It computes its usable available disk space subtactively, rather than additively; that is, it ensures that it uses all of the available space, except for a reserved portion of disk.

GSE documentation suggests that storage is indefinitely large, which I assume means that the "disk" size of the bucket will appear as some ridiculous or unexpected number. What actually happens? Is there a way to instruct the gcsfuse binary to set a maximum bucket size?

Corbin
  • 328
  • 2
  • 6

1 Answers1

1

Assuming the database uses statfs to find free space, gcsfuse simulates 1 PiB of free space. (This is not guaranteed in the documentation anywhere and is subject to change.)

There are tests that confirms this works on macOS and linux.

jacobsa
  • 439
  • 3
  • 11