From: Daniel Poelzleithner <poelzi@poelzi.org>
To: Bryan Donlan <bdonlan@gmail.com>
Cc: linux-kernel@vger.kernel.org, Simon Horman <horms@verge.net.au>,
Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
Subject: Re: Suggestion: xtime as new inode attribute
Date: Fri, 18 Dec 2009 10:19:25 +0100 [thread overview]
Message-ID: <4B2B491D.2010201@poelzi.org> (raw)
In-Reply-To: <3e8340490912162306m4236569s4e497ad01409c756@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bryan Donlan wrote:
> Why isn't atime sufficient? atime is updated when programs are
> executed, and it's uncommon for executable files to be accessed
> without being executed; for the purposes of determining whether a
> program is needed, it ought to be good enough.
Why atime is not useable is for example that full system backup would
distroy all data. Thinking about grepping for a string in /usr or
/usr/bin because you are searching for something will update all atime
stamps and therefore cause dataloss for this purpose.
> Note that many modern distros use relatime to reduce the (significant)
> overhead of atime; this may account for why you may not be seeing
> atime update for executables; try mounting with -o strictatime if you
> want to see it at work, but beware, as this will bring with it a major
> performance hit - which your proposal would as well :)
The performance impact is one reason of course. As executing is much
more seldom the impact of updating the xtime should be mild enough that
it could be done by default. I don't mount strictatime for this reason, too.
kindly regards
Daniel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIcBAEBAgAGBQJLK0kdAAoJEFYpgV2Roepc35AP/RkT6Q0Nz0qseGboEFYOfwju
NDsyJT2Thw/bm/zwo024TwnyoBOA2o9rGwmIuppsOGijpyuSSwJXVUcnPXoC/Gto
Eb3eMud41qZewFgIRNkur7torWG2k59GmY9AgmKgYbm8L1O81k6Zeesl3aY0SedJ
gF690R7Ktn+Cb+9xMq3g2ip8Vu7TegHHS0L9UtD0zaVRlmqBf1cfZBWpKZJ1ndyG
15/pUBdYoIJavMxgRAbpcpSZfBEJlW1kJpELeIyBCglYkh8j2W5mJVi0PcwUtEzp
cdgVNjQwpqUicYsY7WbG469m2jd7oPl6hCKPJ1oWncaVUyddubU9JHYRAAgTYvMT
fBb/83yxQ6H9DFfwHk7dRGLrko8vhZ3GiDJIYmbWbR5XHa+qr4lwoX1M3NTAp62B
j15hy0Ap2cu58tFhMFoh9pOPY95b5Xs7hVlBcqm2CqSwIOcmO/3f8Vmw1RLlG/F+
0XZ692nmYFPrnKqQAM6mQXuKUI4QGPLlaD2lSyZf3czXD1kTt01SQSvZ7stI3aA5
hEgYDm+zJHR76W6Wr5JXISQMSCLOiYf5g0gRLF2TIXz5VL2W3NOex+vCnBoEPmXt
hQ6t3x1YWrhE35VV2r4zhxUz+/9wGEncGGOwwdBPmegVW/NrxAwjsa7hPdddG5+4
V9RsTox7UQNQYaxk3PpR
=ixfn
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-12-18 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 18:57 Suggestion: xtime as new inode attribute Daniel Poelzleithner
2009-12-17 1:00 ` Simon Horman
2009-12-17 5:47 ` Jeffrey Hundstad
2009-12-18 9:27 ` Daniel Poelzleithner
2009-12-18 14:59 ` tytso
2009-12-17 7:06 ` Bryan Donlan
2009-12-18 9:19 ` Daniel Poelzleithner [this message]
2009-12-19 0:19 ` Junio C Hamano
2009-12-19 1:48 ` Frans Pop
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B2B491D.2010201@poelzi.org \
--to=poelzi@poelzi.org \
--cc=bdonlan@gmail.com \
--cc=horms@verge.net.au \
--cc=jeffrey.hundstad@mnsu.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox