public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Timothy Shimmin <tes@sgi.com>
Cc: Martin Steigerwald <Martin@lichtvoll.de>, xfs@oss.sgi.com
Subject: Re: Creation time in XFS
Date: 01 Oct 2007 11:30:01 +0200	[thread overview]
Message-ID: <p73ve9r6v3a.fsf@bingen.suse.de> (raw)
In-Reply-To: <470042DC.2040009@sgi.com>

Timothy Shimmin <tes@sgi.com> writes:

> No XFS does not support creation time. It just has the regular
> atime,mtime and ctime.
> There are no plans that I've heard to support it.
> Not much involved to support it AFAICT but it would either involve
> changing the ondisk format of the inode or storing it in an EA.

If you ever change the on disk format adding a file type similar to ext3
to directories could also greatly speed up find in many cases.

> I wonder how this creation time is being exported currently?

I don't think it is at all currently:

% gid i_crtime
fs/udf/udf_i.h:21:#define UDF_I_CRTIME(X)               ( UDF_I(X)->i_crtime )
include/linux/ext4_fs.h:344:    __le32  i_crtime;       /* File Creation time */
include/linux/ext4_fs_i.h:160:  struct timespec i_crtime;
include/linux/udf_fs_i.h:20:    struct timespec         i_crtime;
fs/ext4/ialloc.c:566:   inode->i_mtime = inode->i_atime = inode->i_ctime = ei->i_crtime =
fs/ext4/inode.c:2705:   EXT4_EINODE_GET_XTIME(i_crtime, ei, raw_inode);
fs/ext4/inode.c:2792:   EXT4_EINODE_SET_XTIME(i_crtime, ei, raw_inode);

-Andi

  reply	other threads:[~2007-10-01  9:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-30 19:24 Creation time in XFS Martin Steigerwald
2007-10-01  0:44 ` Timothy Shimmin
2007-10-01  9:30   ` Andi Kleen [this message]
2007-10-02  5:55     ` Timothy Shimmin
2007-10-02  9:25     ` David Chinner
2007-10-02  9:38       ` Christoph Hellwig
2007-10-02 21:31         ` David Chinner
2007-10-01  2:59 ` Eric Sandeen

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=p73ve9r6v3a.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=Martin@lichtvoll.de \
    --cc=tes@sgi.com \
    --cc=xfs@oss.sgi.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