According to our Moderators this forum is for the user community only with no WD tech people reading; hopefully a moderator will pass this along but generally when you ask such a question none of us (the community) can answer with any resolution.
However, now that you have discovered this workaround, I think I can guess the reason. Lets bring the mounting options over from the other post.
Current versions of Linux, Mac OS X, Solaris, FreeBSD, NetBSD, and OpenBSD support a noatime mount option, which causes the atime field never to be updated. This breaks compliance with POSIX.
Current versions of the Linux kernel support four mount options, which can be specified in fstab:
- strictatime (formerly atime, and formerly the default; strictatime as of 2.6.30) – always update atime
- relatime (“relative atime”, introduced in 2.6.20 and the default as of 2.6.30) – only update atime under certain circumstances (explained below)
- nodiratime – never update atime of directories, but do update atime of other files
- noatime – never update atime of any file or directory; implies nodiratime; highest performance, but least compatible
strictatime accords with POSIX. File systems mounted with the noatime option do not update the atime on reads, while
So from looking at our mouting options, relatime is the norm which is the answer to your question of why they used it.
the relatime option provides for updates only if the previous atime is older than the mtime or ctime, or the previous atime is over 24 hours in the past.
Changing it to noatime implying nodiratime means never update atime of any file or directory.
Many users use noatime without problem, so long as they do not use an application which depends on atime, and this offers some benefits over relatime (no writing of atime ever on read).
Nice workaround, however I need to check if I need atime updates