Message360952
| Author |
fweimer |
| Recipients |
David.Edelsohn, Dormouse759, fweimer, hroncok, vstinner |
| Date |
2020-01-29.11:19:15 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1580296755.33.0.903971589055.issue39460@roundup.psfhosted.org> |
| In-reply-to |
|
| Content |
I believe you might be observing an XFS limitation in combination with a Linux VFS bug.
On disk, XFS only supports 32-bit timestamps:
typedef struct xfs_timestamp {
__be32 t_sec; /* timestamp seconds */
__be32 t_nsec; /* timestamp nanoseconds */
} xfs_timestamp_t;
This is on the roadmap being fixed.
However, the Linux VFS code does not appear to know about this. It caches the full 64-bit value. You only see the truncated value if it is read back from disk:
# touch -t 222201020304 /tmp/t
# ls -l /tmp/t
-rw-r--r--. 1 root root 0 Jan 2 2222 /tmp/t
# echo 3 > /proc/sys/vm/drop_caches
# ls -l /tmp/t
-rw-r--r--. 1 root root 0 Oct 19 1949 /tmp/t
This is a bug in the Linux VFS layer. |
|