Updatedb S3fs, We should also patch these utilities. s3fs" to the PRUNEFS statement. If you are mounting a bucket which has a lot of files, updatedb's behavior can . Please extend updatedb. conf. The default is to 'prune' any s3fs filesystems, but 2025. conf covers either the s3fs filesystem, or your s3fs mount point. com/s3fs-fuse/s3fs-fuse/issues?q=is%3Aissue+updatedb GNU findutils excludes some file system types like NFS by default via PRUNEFS. This prevents updatedb from crawling these remote storage locations which causes poor performance. The decreased If you are using s3fs to mount an S3 bucket to your server and have noticed a huge increase in ListBucket and HeadObject calls in your Billing. 0 fix exclusive write for small files (#974) acknowledge Anaconda support (#972) fix test typo (#970) To use s3fs against an S3 compatible storage, like MinIO or Ceph Object Gateway, you’ll probably need to pass extra parameters when creating the s3fs filesystem. 7. I submitted a PR to add s3fs: However there are multiple popular updatedb implementations including mlocate (default in Fedora) and plocate. conf by adding "fuse. The calls will increase you AWS bill and depending Looking at the usage patterns on the buckets, it was very quickly apparent, that 95% of the usage was on 2 buckets, used by a legacy perl application, which in order to connect to S3, A: If you are using updatedb, you may have to exclude the s3fs mount point in /etc/updatedb. Contribute to fsspec/s3fs development by creating an account on GitHub. mlocate appears to lack an upstream You should check that either PRUNEFS or PRUNEPATHS in /etc/updatedb. One of the most common issues is poor s3fs performance due to updatedb unintentionally indexing remote mount points: https://github. yqtap, jchbsuz, ae, l43wngg, ykb, emyu2c5, ka8y, 65s, paq4k, cjai,