From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Peter Staubach <staubach@redhat.com>
Cc: Alexandre Ratchov <alexandre.ratchov@bull.net>,
linux-ext4@vger.kernel.org, nfsv4@linux-nfs.org
Subject: Re: rfc: [patch] change attribute for ext3
Date: Thu, 14 Sep 2006 09:56:20 -0400 [thread overview]
Message-ID: <1158242180.5308.24.camel@lade.trondhjem.org> (raw)
In-Reply-To: <45095D1B.8040201@redhat.com>
On Thu, 2006-09-14 at 09:46 -0400, Peter Staubach wrote:
> Wouldn't the generation count work better than ctime to differentiate
> between
> instances of files using the same inode number? That way, there wouldn't be
> a clock resolution issue.
No. This is about distinguishing updates to the metadata/data of the
same instance. It is exactly what ctime was supposed to do, but ctime
relies on a clock which usually has too poor time resolution, may not be
monotonic, etc...
Cheers,
Trond
next prev parent reply other threads:[~2006-09-14 13:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 16:42 rfc: [patch] change attribute for ext3 Alexandre Ratchov
2006-09-13 18:11 ` Trond Myklebust
2006-09-13 18:30 ` Alexandre Ratchov
2006-09-13 19:06 ` Trond Myklebust
2006-09-13 20:31 ` Randy.Dunlap
2006-09-14 9:23 ` Andreas Dilger
2006-09-14 13:48 ` Alexandre Ratchov
2006-11-14 22:17 ` Andreas Dilger
2006-11-24 0:23 ` Andreas Dilger
2006-11-28 19:00 ` J. Bruce Fields
2006-11-28 22:06 ` Andreas Dilger
2006-09-14 13:46 ` Peter Staubach
2006-09-14 13:56 ` Trond Myklebust [this message]
2006-09-14 14:06 ` Alexandre Ratchov
2006-12-14 1:24 ` Andreas Dilger
2006-12-14 1:52 ` J. Bruce Fields
2006-12-14 16:48 ` Trond Myklebust
2006-12-14 23:04 ` Andreas Dilger
2006-09-13 19:31 ` Andreas Dilger
2006-09-14 1:24 ` J. Bruce Fields
2006-09-14 13:21 ` Alexandre Ratchov
2006-09-14 21:01 ` Andreas Dilger
2006-09-15 10:19 ` Alexandre Ratchov
2006-09-15 16:18 ` Andreas Dilger
2006-11-29 18:54 ` [RFC] [patch 0/3] change attribute for ext4 Jean-Noel Cordenner
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=1158242180.5308.24.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=alexandre.ratchov@bull.net \
--cc=linux-ext4@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=staubach@redhat.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).