Sstrhsrtj

The POSIX standard only defines three distinct timestamps to be stored for each file: the time of last data access, the time of last data modification, and the time the file status last changed.

That said, modern Linux filesystems, such as ext4, Btrfs and JFS, do store the file creation time (aka birth time), but use different names for the field in question (crtime in ext4, otime in Btrfs and JFS). However, currently Linux does not provide a kernel API for accessing the file creation times, even on filesystems supporting them.

As Craig Sanders and Mohsen Pahlevanzadeh pointed out, stat does support the %w and %W format specifiers for displaying the file birth time (in human readable format and in seconds since Epoch respectively). However, stat itself accesses the birth time via the get_stat_birthtime() provided by gnulib (in lib/stat-time.h), which gets the birth time from the st_birthtime and st_birthtimensec fields of the stat structure returned by the stat() system call. While for instance BSD systems (and in extension OS X) provide st_birthtime via stat, Linux does not. This is why stat -c '%w' file outputs - (indicating an unknown creation time) on Linux even for filesystems which do store the creation time internally.

As Stephane Chazelas points out, some filesystems, such as ntfs-3g, expose the file creation times via extended file attributes.

TLDR; Use stap ("SystemTap") to create your own kernel API. Demo of ext4 creation time extraction below.

You can extract the ext4 creation times on Fedora 19 systems. Here's mine:

$ uname -a

Linux steelers.net 3.11.1-200.fc19.i686.PAE #1 SMP Sat Sep 14 15:20:42 UTC 2013 i686 i686 i386 GNU/Linux

It's clear that the inodes on my ext4 partitions have the creation time. Here's a shell script that determines the inode associated with a filename and then augments the stat output with the creation time by using stap ("systemtap").

NB: This is just a demo and hugely inefficient since a kernel module is created, loaded, and unloaded for every execution. This is also probably very fragile as no error checking is performed. A proper kernel API would be preferable, but this script could be made much more efficient and read the creation times of multiple files/inodes.

[contents of stap_stat.sh]

#/bin/sh



my_inode_str=$(stat --printf="%i" $1)



stap - << end_of_stap_script

global my_offsetof

probe begin {

  system("stat $1");

  my_offsetof = &@cast(0,"struct ext4_inode_info")->vfs_inode;

}

probe kernel.function("ext4_getattr@fs/ext4/inode.c") {

  probe_inode=$dentry->d_inode;

  if (@cast(probe_inode, "struct inode")->i_ino == $my_inode_str) {

    my_i_crtime = &@cast(probe_inode - my_offsetof,"struct ext4_inode_info")->i_crtime;

    printf("CrTime: %s GMTn", ctime(@cast(my_i_crtime, "timespec")->tv_sec));

    printf("CrTime (nsecs): %dn", @cast(my_i_crtime, "timespec")->tv_nsec);

    exit();

  }

}

end_of_stap_script

Here's a demo:

$ ll testfile

ls: cannot access testfile: No such file or directory

$ touch testfile

$ ./stap_stat.sh testfile

  File: ‘testfile’

  Size: 0           Blocks: 0          IO Block: 4096   regular empty file

Device: fd02h/64770d    Inode: 4850501     Links: 1

Access: (0664/-rw-rw-r--)  Uid: ( 1001/    Rick)   Gid: ( 1001/    Rick)

Context: unconfined_u:object_r:user_home_t:s0

Access: 2013-09-28 06:17:04.221441084 -0400

Modify: 2013-09-28 06:17:04.221441084 -0400

Change: 2013-09-28 06:17:04.221441084 -0400

 Birth: -

CrTime: Sat Sep 28 10:17:04 2013 GMT

CrTime (nsecs): 220441085

$ ll testfile

-rw-rw-r--. 1 Rick Rick 0 Sep 28 06:17 testfile

$ cat - >> testfile 

Now is the time ...

$ ll testfile 

-rw-rw-r--. 1 Rick Rick 20 Sep 28 06:18 testfile

$ ./stap_stat.sh testfile

  File: ‘testfile’

Device: fd02h/64770d    Inode: 4850501     Links: 1

Access: (0664/-rw-rw-r--)  Uid: ( 1001/    Rick)   Gid: ( 1001/    Rick)

Context: unconfined_u:object_r:user_home_t:s0

Access: 2013-09-28 06:17:04.221441084 -0400

Modify: 2013-09-28 06:18:33.684374740 -0400

Change: 2013-09-28 06:18:33.684374740 -0400

 Birth: -

CrTime: Sat Sep 28 10:17:04 2013 GMT

CrTime (nsecs): 220441085

$ cat testfile 

Now is the time ...

$ ./stap_stat.sh testfile

  File: ‘testfile’

  Size: 20          Blocks: 8          IO Block: 4096   regular file

Device: fd02h/64770d    Inode: 4850501     Links: 1

Access: (0664/-rw-rw-r--)  Uid: ( 1001/    Rick)   Gid: ( 1001/    Rick)

Context: unconfined_u:object_r:user_home_t:s0

Access: 2013-09-28 06:19:12.199349463 -0400

Modify: 2013-09-28 06:18:33.684374740 -0400

Change: 2013-09-28 06:18:33.684374740 -0400

 Birth: -

CrTime: Sat Sep 28 10:17:04 2013 GMT

CrTime (nsecs): 220441085

$ mv testfile testfile2

$ ./stap_stat.sh testfile2 

  File: ‘testfile2’

  Size: 20          Blocks: 8          IO Block: 4096   regular file

Device: fd02h/64770d    Inode: 4850501     Links: 1

Access: (0664/-rw-rw-r--)  Uid: ( 1001/    Rick)   Gid: ( 1001/    Rick)

Context: unconfined_u:object_r:user_home_t:s0

Access: 2013-09-28 06:19:12.199349463 -0400

Modify: 2013-09-28 06:18:33.684374740 -0400

Change: 2013-09-28 06:20:45.870295668 -0400

 Birth: -

CrTime: Sat Sep 28 10:17:04 2013 GMT

CrTime (nsecs): 220441085

$ 

In ext4 it is possible; because ext4 file-system stores the file creation time. But still, you will find that the stat command is unable to show the date, because I think the kernel is not having any APIs for this.

Anyway, the file birth time is stored in ext4 and you can find it out, although not by a direct method, but by using debugfs

sudo debugfs -R "stat /ABSOLUTE/PATH" /dev/sdxX | grep crtime

In theory, with GNU stat you could use stat -c '%w' or %W to get a file's creation date (aka birthtime).

In practice, most filesystems do not record that information and the linux kernel does not provide any way of accessing it.

The closest you can get is the file's ctime, which is not the creation time, it is the time that the file's metadata was last changed.

Linux Weekly News had an interesting article about this a few years back - http://lwn.net/Articles/397442/

stat --printf='%w' yourfile   #human readable



stat --printf='%W' yourfile   #seconds from Epoch , 0 if unknown

Difference between FreeBSD and GNULinux on stat command:

If you call stat command in GNULinux it invokes the -x option, but in FreeBSD, you yourself should invoke the -x option.

See also What file systems on Linux store the creation time?

Notes: --printf is very useful in scripting....!

In OS X you can use ls -lU, stat -f%B, GetFileInfo -d, or mdls -n kMDItemFSCreationDate:

$ ls -lU

total 0

-rw-r--r--  1 lauri  staff  0 Apr 25 03:58 a

$ stat -f%B a

1398387538

$ stat -f%SB -t %Y%m%d%H%M a

201404250358

$ GetFileInfo -d a

04/25/2014 03:58:58

$ mdls -n kMDItemFSCreationDate a

kMDItemFSCreationDate = 2014-04-25 00:58:58 +0000

Check this out:

# the last arg is the device to scan in.

debugfs -R 'stat /home/renich/somefile' /dev/sda1

BTW, this works on ext4 only. I haven't found a solution for BtrFS... yet ;)