Behemoths periodically run out of inodes about community-build HOT 4 CLOSED

Hmm — I remember talking with @cunei once about the possibility of shallow-cloning. I'll see if I can dig that conversation up.

from community-build.

Alternatively we can create a new EBS volume with a new file system where we explicitly specify the number of inodes on creation (https://askubuntu.com/questions/600159/how-can-i-create-an-ext4-partition-with-an-extra-large-number-of-inodes), then copy over the files.

from community-build.

at present, on each behemoth I need to blow away the community build directories under workspace every 2 months, something like that. it's very little burden

from community-build.

closing, as I think the status quo here is okay. we've recently added JDK 20 which increases the pressure somewhat, so we'll see, but in the meantime, I don't think this needs to stay open.

from community-build.