public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Björn JACKE" <bjacke@sernet.de>
To: Theodore Tso <tytso@mit.edu>
Cc: ext3-users@redhat.com, linux-ext4@vger.kernel.org
Subject: Re: creation time stamps for ext4 ?
Date: Thu, 5 Oct 2006 21:23:12 +0200	[thread overview]
Message-ID: <E1GVYnq-00004v-00@intern.SerNet.DE> (raw)
In-Reply-To: <20061005165504.GA23727@thunk.org>

On 2006-10-05 at 12:55 -0400 Theodore Tso sent off:
> > I've given this some thought for adding 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.
> 
> So there are VFS and glibc changes necessary to make this be useful.
> But that doesn't prevent us from reserving space in the inode and
> starting to fill it in with the creation time, although it may be
> quite a while before it will be easily available to user programs like
> Samba.

yes, probably. But it's a reasonable effort to start that at some 
time. It's good if ext3 developers have it in mind already now.
Should I open a feature request at bugzilla.kernel.org for the needed 
VFS changes?

Bjoern

  reply	other threads:[~2006-10-05 19:22 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 [this message]
2006-10-05 20:07     ` Andreas Dilger

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=E1GVYnq-00004v-00@intern.SerNet.DE \
    --to=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