Bring a directory up to date
A pipeline wrote files straight to the bucket and you need them visible in the filesystem now. Here is how to check, and how to force an update.
Changes written straight to the bucket normally appear within seconds, through change notifications. This walkthrough covers the cases where they don’t, and what to do.
1. Is it the client’s cache?
NFS clients remember directory contents and missing names for a few seconds. Wait a moment and list the directory again. If new files keep appearing late on a client that needs them promptly, remount it with less caching:
sudo mount -t nfs -o vers=4,actimeo=1,lookupcache=none blixt-server:/ /mnt/blixt
2. Ask BlixtFS to check the directory
setfattr -n bfs.fsck_request -v 1 /mnt/blixt/aws/my-bucket/incoming
This queues a consistency check of incoming and everything below it. For a
single directory level, use -v shallow.
3. Watch it finish
getfattr -n bfs.fsck_state /mnt/blixt/aws/my-bucket/incoming
The state moves from pending through running to done. Then read the
summary:
getfattr -n bfs.fsck /mnt/blixt/aws/my-bucket/incoming
4. Fix the cause
If you need to force updates often, find out why notifications aren’t arriving:
- The log says whether notifications were set up for the bucket, and why not if they weren’t.
- Some providers need extra setup (Google Cloud Storage) or have no notifications at all (CoreWeave).
See Troubleshooting.