SMB and "birth" date on Linux client

[ascl]

I haven't been able to find much on this, but the issue I am seeing is that file birth times are not visible on Linux via CIFS.

I am running TrueNAS Core 13.0 U5.3 (x11sae-m w/ xeon e3-1240L v5, 32GB ECC RAM, and a mix of drives), testing with Win 11, and Linux 6.1(Alpine containers). My share looks like this:

Code:

[Multimedia]
    ea support = No
    guest ok = Yes
    level2 oplocks = No
    oplocks = No
    path = /mnt/Tank/Multimedia
    read only = No
    smbd max xattr size = 2097152
    strict locking = Yes
    vfs objects = zfs_space fruit streams_xattr zfsacl
    fruit:resource = stream
    fruit:metadata = stream
    nfs4:chown = true
    ixnas:dosattrib_xattr = false

And when I stat a file from a linux client, I see something like this:

Code:

$ stat desktop.ini
  File: desktop.ini
  Size: 504             Blocks: 9          IO Block: 8192   regular file
Device: 0,94    Inode: 69815       Links: 1
Access: (0770/-rwxrwx---)  Uid: (   80/ UNKNOWN)   Gid: ( 1000/   users)
Access: 2023-12-02 10:08:14.615166800 +1100
Modify: 2018-10-11 06:15:09.000000000 +1100
Change: 2019-09-22 08:48:28.176071572 +1000
 Birth: -

But if I check properties in windows it correctly reflects what TrueNAS says:

Code:

$ stat -x desktop.ini
  File: "desktop.ini"
  Size: 504          FileType: Regular File
  Mode: (0770/-rwxrwx---)         Uid: (   80/     www)  Gid: ( 1000/sharedfiles)
Device: 1329830751,318046300   Inode: 69815    Links: 1
Access: Sat Dec  2 10:08:14 2023
Modify: Thu Oct 11 06:15:09 2018
Change: Sun Sep 22 08:48:28 2019
 Birth: Thu Oct 11 06:15:09 2018

Are there options I can use on the TrueNAS side to expose this to the Linux clients, or is it a client side problem? Any help would be appreciated!

 

[winnielinnie]

Works for me from three different Linux clients.

How did you mount the share on your Linux client?

CIFS kernel module or via GVFS/KIO?

What mount options did you use?

 

[ascl]

The above test was actually via NFS, using SMB I do see the birth date. So this problem is specific to my Roon Server, which is running Linux, and uses SMB/CIFS, and I don't have visibility into how they mount the SMB filesystem.

Thanks for confirming it works for you, that is very helpful. I'll work with Roon support to figure out what's going on on their end. It seems Roon connects using SMB 2.1 vs the SMB 3.11 everything else uses.

Thank you! Not "resolved" per se, but certainly a step in the right direction.