We've been seeing messages on our build servers where we fail to reserve space for the compression property and thus fail to create the property at inode creation time. This is because we do not pre-reserve the space, instead opting to use NO_FLUSH which can fail transiently, and create these messages. Instead just pre-reserve an extra items worth of space, and use that space when we inherit our property. We only have the compression property right now, so we can get away with this, and if we add any more properties we have the backup method of doing the NO_FLUSH reservation. However in the future we may want to take a more nuanced approach to property space reservation if we add a bunch of new properties. Thanks, Josef
