lkml.org 
[lkml]   [2007]   [Aug]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 00/23] per device dirty throttling -v8

* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> > Can you give examples of backup solutions that rely on atime being
> > updated? I can understand backup tools using mtime/ctime for
> > incremental backups (like tar + Amanda, etc), but I'm having trouble
> > figuring out why someone would want to use atime for that.
>
> HSM is the usual one, and to a large extent probably why Unix
> originally had atime. Basically migrating less used files away so as
> to keep the system disks tidy.

atime is used as a _hint_, at most and HSM sure works just fine on an
atime-incapable filesystem too. So it's the same deal as "add user_xattr
mount option to the filesystem to make Beagle index faster". It's now:
"if you use HSM storage add the atime mount option to make it slightly
more intelligent. Expect huge IO slowdowns though."

The only remotely valid compatibility argument would be Mutt - but even
that handles it just fine. (we broke way more software via noexec)

Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-08-05 09:31    [W:1.697 / U:0.280 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site