ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: Joel Becker <jlbec@evilplan.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/1] ocfs2-tools: support strictatime in ocfs2
Date: Sat, 26 Mar 2011 14:42:47 -0700	[thread overview]
Message-ID: <20110326214246.GA8837@noexit> (raw)
In-Reply-To: <1299065437-6594-1-git-send-email-tiger.yang@oracle.com>

On Wed, Mar 02, 2011 at 07:30:37PM +0800, Tiger Yang wrote:
> Strictatime was introduced into vfs, so this patch adding support
> to it in ocfs2. Now we have three types behavior about update atime,
> noatime, relatime and strictatime. With strictatime, the minimum
> update interval is specified by atime_quantum, which defaults to 60 secs.

<snip>

> diff --git a/mount.ocfs2/opts.c b/mount.ocfs2/opts.c
> index 5ecd36b..96037da 100644
> --- a/mount.ocfs2/opts.c
> +++ b/mount.ocfs2/opts.c
> @@ -78,12 +78,12 @@ static const struct opt_map opt_map[] = {
>    { "mand",	0, 0, MS_MANDLOCK },	/* Allow mandatory locks on this FS */
>    { "nomand",	0, 1, MS_MANDLOCK },	/* Forbid mandatory locks on this FS */
>    { "loop",	1, 0, MS_LOOP	},	/* use a loop device */
> -  { "atime",	0, 1, MS_NOATIME },	/* Update access time */

	Won't this break people saying 'mount -o noatime'?

Joel

-- 

"Maybe the time has drawn the faces I recall.
 But things in this life change very slowly,
 If they ever change at all."

			http://www.jlbec.org/
			jlbec at evilplan.org

  reply	other threads:[~2011-03-26 21:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 11:27 [Ocfs2-devel] [PATCH 0/2] support strictatime in ocfs2 Tiger Yang
2011-03-02 11:30 ` [Ocfs2-devel] [PATCH 1/1] ocfs2-tools: " Tiger Yang
2011-03-26 21:42   ` Joel Becker [this message]
2011-03-28  8:37     ` Tiger Yang
2011-03-02 11:32 ` [Ocfs2-devel] [PATCH 1/1] ocfs2: clean up mount option about atime in ocfs2.txt Tiger Yang
2011-03-26 21:44   ` Joel Becker
2011-03-28  8:50     ` Tiger Yang
2011-05-24  6:56   ` Joel Becker

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=20110326214246.GA8837@noexit \
    --to=jlbec@evilplan.org \
    --cc=ocfs2-devel@oss.oracle.com \
    /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;
as well as URLs for NNTP newsgroup(s).