From: Andreas Dilger <adilger@clusterfs.com>
To: "AVANTIKA R. MATHUR" <mathur@linux.vnet.ibm.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Ext4 devel interlock meeting minutes (Dec. 13 2006)
Date: Wed, 13 Dec 2006 17:08:34 -0700 [thread overview]
Message-ID: <20061214000834.GB5937@schatzie.adilger.int> (raw)
In-Reply-To: <45809003.5060403@linux.vnet.ibm.com>
On Dec 13, 2006 15:42 -0800, AVANTIKA R. MATHUR wrote:
> - Change Attribute:
> -- Andreas asked the bull team why a new field in the inode is
> necessary rather than using the i_version field, and also mentioned that
> all code changes can be in mark_inode_dirty.
> -- The ctime cannot be used for the change attribute because if the
> server clock is incorrect, the ctime can go backwards in time.
> -- semantics needed: nfsv4 and bull team require 32 bits, clusterfs
> needs 64 bits.
Minor clarification. Bull patch for NFSv4 only uses 32 bits, but apparently
the NFSv4 spec calls for 64 bits.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
prev parent reply other threads:[~2006-12-14 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 23:42 Ext4 devel interlock meeting minutes (Dec. 13 2006) AVANTIKA R. MATHUR
2006-12-14 0:08 ` Andreas Dilger [this message]
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=20061214000834.GB5937@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mathur@linux.vnet.ibm.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