From: David Chinner <dgc@sgi.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Timothy Shimmin <tes@sgi.com>,
Martin Steigerwald <Martin@lichtvoll.de>,
xfs@oss.sgi.com
Subject: Re: Creation time in XFS
Date: Tue, 2 Oct 2007 19:25:10 +1000 [thread overview]
Message-ID: <20071002092509.GF995458@sgi.com> (raw)
In-Reply-To: <p73ve9r6v3a.fsf@bingen.suse.de>
On Mon, Oct 01, 2007 at 11:30:01AM +0200, Andi Kleen wrote:
> 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.
Sure, but that's the directory structure, not inode structure.
They have different versioning methods, and so can be modified
independently.
FWIW, I haven't forgotten abou thtis request, Andi ;) I'll be
modifying the directory structure for CRCs relatively soon, and I
plan to do that modification at the same time so I only need a
single version bump for both....
> > I wonder how this creation time is being exported currently?
>
> I don't think it is at all currently:
So what is the point? Forensic analysis?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-10-02 9:25 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
2007-10-02 5:55 ` Timothy Shimmin
2007-10-02 9:25 ` David Chinner [this message]
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=20071002092509.GF995458@sgi.com \
--to=dgc@sgi.com \
--cc=Martin@lichtvoll.de \
--cc=andi@firstfloor.org \
--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