On 2016-02-23 12:34, Nazar Mokrynskyi wrote:
Wow, this is interesting, didn't know it.
I'll probably try noatime instead:)
For what it's worth, due to how it's implemented on almost every UNIX
derived system in existence (including Linux), atimes are essentially
useless. A majority of the software that has used them over the years
has mad the flawed assumption that the atime only gets updated when the
file data is read or modified, when they actually get updated when ever
the file data is read or modified, and when the metadata is modified
(and in some old UNIX systems, the update on file data modification was
simply implemented as a cascade effect from the mtime getting updated).
Mutt is one of the only publicly available programs I know of that
uses them, and it makes this same flawed assumption. The only software
I know of that uses them right is tmpwatch and tmpreaper, which use them
to clean up /tmp and similar directories when files there haven't been
touched in a long time, and even those have the option to not use atimes.
Now, long rant aside, you may want to also look into the 'lazytime'
mount option. It won't reduce fragmentation, but it should improve
performance overall, the only downsides are that mtimes might be
incorrect after a crash, and it's only available in newer kernels (I
think it got added in 4.0 or 4.1, but I'm not certain).
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
