The page has unconfirmed changes. Use the buttons below to see older versions.
Hashbert issues and bugs
Tested filesystems
Primarily tested on linux.
|
Works
|
Timestamp resolution
|
Other notes
|
ext4:
|
OK
|
Seconds with 9-decimals
|
NTFS:
|
OK
|
Seconds with 7-decimals
|
FAT32
|
Not OK (localtime issue (see below))
|
Seconds floored to closest even second.
|
Does not support soft-links
|
exFat:
|
|
Seconds with 2-decimals
|
Does not support soft-links
|
UDF on linux:
|
Not OK (tested 2017) (seems to be a bug in linux (it might be fixed by the time you read this))
|
Other filesystems (filesystem / operating system combinations) haven't been tested.
Issues
Localtime issue
Some filesystems (like FAT32) uses DOS-time where all timestamps are interpreted as localtime (which means that a timestamp is interpreted different when you change timezone or when
DST switches).
On linux there seems to be problem with
Universal_Disk_Format. I the src-code: when using "readdir" to read an directory entry, entry->d_type should be equal to DT_DIR, but it isn't. (Noted 2017 (so it might be fixed by the time you read this))