From: Steve French <smfrench@gmail.com>
To: Jeremy Allison <jra@samba.org>
Cc: Andreas Dilger <adilger@sun.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
samba-technical <samba-technical@lists.samba.org>
Subject: Re: ext4 - getting at birth time (file create time) and getting/setting nanosecond time stamps and utime
Date: Mon, 19 Oct 2009 14:37:02 -0500 [thread overview]
Message-ID: <524f69650910191237w1ec3b6efoef1f21d00e737cf4@mail.gmail.com> (raw)
In-Reply-To: <20091019185855.GC15201@samba1>
On Mon, Oct 19, 2009 at 1:58 PM, Jeremy Allison <jra@samba.org> wrote:
> On Mon, Oct 19, 2009 at 12:55:29PM -0600, Andreas Dilger wrote:
>>
>> As for _updating_ create time, isn't that sort of defeating the purpose
>> of create time?
>
> Yes, you would think so, wouldn't you. Unfortunately that's
> the way Windows behaves (create time can be updated) so that's
> what we have to emulate. If does indeed make no sense (it's
> just another timestamp meta-data that can't be used for auditing
> at that point).
Updating create time does make it harder to use for auditing, but
I expect that 20 years ago when this was added someone was thinking
about making sure you could preserve all attributes on backup/restore
especially for a system restore after disk failure - and end up with
the same file metadata as when you started.
--
Thanks,
Steve
next prev parent reply other threads:[~2009-10-19 19:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 17:17 ext4 - getting at birth time (file create time) and getting/setting nanosecond time stamps and utime Steve French
2009-10-19 18:55 ` Andreas Dilger
2009-10-19 18:58 ` Jeremy Allison
2009-10-19 19:37 ` Steve French [this message]
2009-10-19 19:12 ` Zach Brown
2009-10-19 20:49 ` Jamie Lokier
2009-10-19 19:45 ` Steve French
2009-10-19 20:11 ` Andreas Dilger
2009-10-19 22:24 ` Steve French
2009-10-19 23:12 ` Andreas Dilger
2009-10-20 3:31 ` Steve French
2009-10-20 12:44 ` jim owens
2009-10-20 20:33 ` Andreas Dilger
2009-10-20 20:49 ` Steve French
2009-10-20 20:59 ` Sunil Mushran
2009-10-20 21:11 ` Steve French
2009-10-20 21:23 ` Sunil Mushran
2009-10-20 21:37 ` Steve French
2009-10-20 21:49 ` Sunil Mushran
2009-10-20 21:56 ` Steve French
2009-10-20 22:16 ` Sunil Mushran
2009-10-21 23:45 ` Mingming
2009-10-21 11:59 ` Henrik Nordstrom
2009-10-21 15:36 ` Steve French
2009-10-21 18:56 ` Brad Boyer
2009-10-21 23:03 ` Björn Jacke
2009-10-22 21:50 ` Steve French
2009-10-21 0:44 ` Andreas Dilger
2009-10-21 23:42 ` Mingming
2009-10-20 21:10 ` jim owens
2009-10-20 0:41 ` Mingming
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=524f69650910191237w1ec3b6efoef1f21d00e737cf4@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=adilger@sun.com \
--cc=jra@samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
/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;
as well as URLs for NNTP newsgroup(s).