Does anyone have experience with running Plone in a datacenter with specialised filesystems?
One of our clients who we help with technical issues has a Plone site with a very large blobstorage (100000+ files). The system administration is running most of the systems on a SAN, which until recently was using ext4. Now they've switched SAN suppliers and the new filesystem is a 'high performance optimised' etc. filesystem, but has a smart way of splitting metadata and data in separate storage locations, for which space is reserved in advanced. And they made a miscalculation.
Only after the migration they found out Plone is storing blobs in deeply nested subdirectories (requiring many inodes and other metadata per blob), but backing up the blobstorage to the SAN regularly using collective.recipe.backup which uses rsync with hardlinks makes things worse. I.e. they were very quickly running out of inodes.
Blobstorage moved from lawn to bushy layout years ago because from what I understood filesystems at that time didn't like 50000 files in one directory. The above is I think an example where advancements in filesystem technology is causing the opposites. 80% of the blobstorages in the world will probably be hosted on a unix/linux variation and ext4. There is the layout strategy in ZODB/blobstorage and there was a migration tool provided to move between bushy and lawny, but these are two opposites. Did anyone have a need in the last years to have a layout strategy inbetween?