FreeBSD 11 and 4+ GB files on optical disc

[David Christensen]

freebsd-questions:

I have a computer:

dpchrist at freebsd:/usr/home/dpchrist $ freebsd-version
11.0-RELEASE-p7

dpchrist at freebsd:/usr/home/dpchrist $ uname -a
FreeBSD freebsd 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu 
Sep 29 03:40:55 UTC 2016 
root at releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  i386


I periodically create archive files on Debian 7, encrypt the archive, 
create checksum files, burn the archive and checksum files to optical 
disc, and then verify the contents of the disc.


The checksums verify okay on Debian 7.


But when I put the optical disc into the subject FreeBSD computer and 
browse to it using Xfce and Thunar, the first thing I notice is that the 
archive file is listed twice:

dpchrist at freebsd:/media/HOLGERDANSKE_COM $ ll
total 8388607
drwxr-xr-x  1 root  wheel  -           2048 Feb  9 11:05 ./
drwxr-xr-x  3 root  wheel  uarch          5 Feb  9 14:34 ../
-rw-r--r--  1 root  wheel  -     4294965248 Feb  9 08:52 201701.tar.cpt
-rw-r--r--  1 root  wheel  -     4294965248 Feb  9 08:52 201701.tar.cpt
-rw-r--r--  1 root  wheel  -             49 Feb  9 08:52 201701.tar.cpt.md5
-rw-r--r--  1 root  wheel  -             81 Feb  9 08:52 
201701.tar.cpt.sha256


When I attempt to verify the checksums, they fail:

dpchrist at freebsd:/media/HOLGERDANSKE_COM $ cat 201701.tar.cpt.md5
dd2dfc838c03a1819efceab530a6c7f8 *201701.tar.cpt

dpchrist at freebsd:/media/HOLGERDANSKE_COM $ md5 -c 
dd2dfc838c03a1819efceab530a6c7f8 201701.tar.cpt
MD5 (201701.tar.cpt) = ac49e95889f44adbdaa2f68f4d7bb96e [ Failed ]

dpchrist at freebsd:/media/HOLGERDANSKE_COM $ cat 201701.tar.cpt.sha256
87b0ba7ed7e706f55f571ec73daad0a2ab9820de9db8e0c889ba8541b5b8f40e 
*201701.tar.cpt

dpchrist at freebsd:/media/HOLGERDANSKE_COM $ sha256 -c 
87b0ba7ed7e706f55f571ec73daad0a2ab9820de9db8e0c889ba8541b5b8f40e 
201701.tar.cpt
SHA256 (201701.tar.cpt) = 
10ebce65e89144fe6161b96a43920cf3437a18b34f1e92c7941343fa9a950ad3 [ Failed ]


I suspect that FreeBSD is having problems because the archive file is 
larger than 4 GB (?).


Any comments or suggestions?


TIA,

David