Re: What to do about snapshot-aware defrag

[Duncan <1i5t5.duncan@cox.net>]

Brendan Hide posted on Sun, 01 Jun 2014 01:51:49 +0200 as excerpted:

>> Will option one mean that we always need to mount with noatime or
>> read-only to allow snapshot defragging to do anything?
> 
> That is a very good question. I very rarely have mounts without noatime
> - and usually only because I hadn't thought of it.

Heh, a couple months ago I got tired of having to add noatime to all my 
standard mounts, and decided to patch my kernel to noatime (instead of 
relatime) by default.  I can if I need to still use relatime or 
strictatime, but if they aren't listed, noatime gets added by default, 
now. =:^)

The only remaining problem is that it's not a full default, as noatime 
still shows up in /proc/self/mounts, but avoiding that would have 
complexified the patch, and not being an actual coder (and DEFINITELY not 
a kernel coder), I decided I best leave well enough alone, patching only 
what I had to to avoid having relatime if I omitted the parameter, and 
only what I was reasonably sure I could do without screwing things up, 
based on my limited sysadmin level reading of the sources.

It would sure be nice if there were a kernel config option for that 
default, which would naturally still default to relatime, which is I'm 
sure where most of the distros not already patching it to noatime would 
leave it, as well.

Meanwhile, agreed, a good question that does indeed remain! =:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman