On 2017-12-01 12:13, Andrei Borzenkov wrote:
01.12.2017 20:06, Hans van Kranenburg пишет:
Additional tips (forgot to ask for your /proc/mounts before):
* Use the noatime mount option, so that only accessing files does not
lead to changes in metadata,
Is not 'lazytime" default today? It gives you correct atime + no extra
metadata update cause by update of atime only.
Unless things have changed since the last time this came up, BTRFS does
not support the 'lazytime' mount option (but it doesn't complain about
it either).
Also, lazytime is independent from noatime, and using both can have
benefits (lazytime will still have to write out the inode for every file
read on the system every 24 hours, but with noatime it only has to write
out the inode for files that have changed).
On top of all that though, you generally shouldn't be trusting atime
because:
1. Many people run with noatime (or patch their kernels to default to
noatime instead of relatime), so you can't be certain if the atime is
accurate at all.
2. It has somewhat non-intuitive semantics when dealing with directories.
3. Even without noatime thrown in, you only get 1 day resolution by
default (as per the operation of 'relatime').
4. Essentially nothing uses it other than find (which only has one day
resolution as it's typically used) and older versions of mutt (which use
it because of lazy programming), which is why issue 1 and 3 are the case.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
