If windows share located on NTFS file system mounted to FreeBSD using mount_smbfs, /usr/bin/stat shows atime, mtime and ctime equal, but realy file have three different times. If you try to set mtime of file with odd seconds - it will be writen one second less value - even seconds. When NTFS share mounted to Windows system - all three file time may be different and may have odd seconds in its. How-To-Repeat: root@vic-free#mount_smbfs //tse/temp /mnt root@vic-free#cd /mnt root@vic-free#ls -l total 0 -rwxr-xr-x 1 root wheel 8 Apr 19 11:10 01 root@vic-free#stat 01 83951363 341235132 -rwxr-xr-x 1 root wheel 4294967295 8 "Apr 19 11:10:59 2005" "Apr 19 11:10:59 2005" "Apr 19 11:10:59 2005" 16644 0 0 01 r root@vic-free#touch -mt 01011000.11 01 root@vic-free#stat 01 83951363 341235132 -rwxr-xr-x 1 root wheel 4294967295 8 "Jan 1 10:00:10 2005" "Jan 1 10:00:10 2005" "Jan 1 10:00:10 2005" 16644 0 0 01
Forgot to add that same thing happening on 5.4-STABLE. Victor A. Prylipko vic@liniya.ru http://www.liniya.ru/
One more add: While creating NEW file on smbfs - it CAN have odd seconds in time. Only while CHANGING time it changed to even seconds. Victor A. Prylipko vic@liniya.ru http://www.liniya.ru/
Responsible Changed From-To: freebsd-bugs->freebsd-fs Over to maintainer(s).
4.11 is so far past EOL as this pr is now meaningless. And ntfs has been removed from 10.0 base see http://svnweb.freebsd.org/base/head/sbin/Makefile?view=log&pathrev=247665
This is related to using smbfs on a FreeBSD client to access an NTFS volume on a Windows server, so it is not tied to the NTFS filesystem no longer present in FreeBSD (and smbfs is still in the base system)
batch change: For bugs that match the following - Status Is In progress AND - Untouched since 2018-01-01. AND - Affects Base System OR Documentation DO: Reset to open status. Note: I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.