From 8c77d65341df54bd0d5f623ad8e030f43778b4d6 Mon Sep 17 00:00:00 2001 From: Clement Date: Tue, 25 Jun 2024 23:14:14 +0800 Subject: [PATCH] Added section about relatime --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index c0f0915..0ce9633 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,8 @@ file-o-bot is inspired by the Autoclass feature of Google Cloud Storage buckets. ## Limitations -1. `atime` is disabled on most Linux systems because of it's performance impact to disk performance. The filesystem attempts a write every time it wants to record a new `atime` value, leading to 1000s of writes and reads that cripple the disk. Want to check if your filesystem supports this? Run `$ mount | grep your_mount_path`. If `noatime` is there, you can't use file-o-bot. +1. `atime` is disabled on most Linux systems because of it's performance impact to disk performance. The filesystem attempts a write every time it wants to record a new `atime` value, leading to 1000s of writes and reads that cripple the disk. Want to check if your filesystem supports this? Run `$ mount | grep your_mount_path`. +1. The other option for modern Linux systems is the `relatime` value. `relatime` only updates the access time if the value is older than modified or status change time. It still provides an inaccurate access time value though. 1. This requires a POSIX-compliant storage path for each of the storage mediums, which means you have to configure the mounting separately and maintain them accordingly. There is no fail-safe here. ## Installation