[lkml]   [2010]   [Jun]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: RFC: Exporting NOCMTIME to userspace
Andi Kleen wrote:
> Aleksandr Koltsoff <> writes:
>> On the other hand, if someone can suggest a way to avoid timestamp
>> updates/causing inode writes, I'm all ears and eyes. (using the
>> block-layer directly or writing a custom fs is not really an elegant
>> solution, IMO).
> I think what would be better would be to have flush intervals
> that specify that m/c time are only flushed with longer
> intervals (similar to the deferred atime that's now in there)
> This would still cause the inode to be written if it gets flushed from
> memory on low memory and occasionally depending on the interval, but
> most of the writes would be gone. All still with the same semantics.

While this might solve the performance aspect of the problem, it will
only migitate the reliability aspect with NANDs, since the inodes will
eventually be flushed anyway (thus causing irreversible wear).

Also, a tunable like you're suggesting would affect all files on a
single filesystem, instead of just a subset of files. Having an option
to "disable" m/ctime updates per file would be optimal in our case,
since we're talking about several years of runtime with the use case.
There are other issues with rrdtool which make this hard, but those are
all solvable without kernel modifications.

That said, the migitative solution would be better than none :-).



 \ /
  Last update: 2010-06-21 11:15    [W:0.029 / U:3.244 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site