5 ms·
This was likely an inode issue on the operating system/kernel and how it represents S3 on the filesystem, especially if you're using something like S3FS.
by terryjsmith 13y ago
This was likely an inode issue on the operating system/kernel and how it represents S3 on the filesystem, especially if you're using something like S3FS.
- rdw 13y agoAh, my brain was somehow not seeing that in the article, but I see it now that I'm looking for it. Thanks!