public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Theodore Tso <tytso@mit.edu>
Cc: "Bj�rn JACKE" <bjacke@sernet.de>,
	ext3-users@redhat.com, linux-ext4@vger.kernel.org
Subject: Re: creation time stamps for ext4 ?
Date: Thu, 5 Oct 2006 14:07:26 -0600	[thread overview]
Message-ID: <20061005200726.GW22010@schatzie.adilger.int> (raw)
In-Reply-To: <20061005165504.GA23727@thunk.org>

On Oct 05, 2006  12:55 -0400, Theodore Tso wrote:
> > I've given this some thought for adding creation time as part of the nsec
> > timestamp patch.  That is more feasable if we move the nsec ctime into
> > the main inode to double as the version field.
> 
> Shoehorning an extra creation time field into the inode is relatively
> easy, but it's also necessary to have system calls to get and set the
> creation time.  The stat structure doesn't have room for the creation
> time, so that means a new version of the stat structure exported the
> kernel, and a new version of the stat structure exported by glibc.

For Lustre and NFSv4, an in-kernel interface is sufficient.

I was thinking that as a preliminary userspace interface we can use
getxattr with a standard name like user.crtime.  Storing the crtime
directly in the inode is more efficient than a separate EA, but it would
also be compatible if Samba wanted to use real EAs to store this in the
absence of large inodes.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.


      parent reply	other threads:[~2006-10-05 20:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1GVUd2-0006O6-00@intern.SerNet.DE>
2006-10-05 15:19 ` creation time stamps for ext4 ? Andreas Dilger
2006-10-05 16:55   ` Theodore Tso
2006-10-05 19:23     ` Björn JACKE
2006-10-05 20:07     ` 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=20061005200726.GW22010@schatzie.adilger.int \
    --to=adilger@clusterfs.com \
    --cc=bjacke@sernet.de \
    --cc=ext3-users@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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