It sure sounds that way. However, I haven't been able to spot a problem
in the FUSE kext thus far. It seems to be setting
VOL_CAP_FMT_2TB_FILESIZE when it should be.
On Mon, 3 Apr 2017, Jim Luther wrote:
On Apr 3, 2017, at 8:56 AM, Scott Talbert
wrote:
It's getting a value fr
An update:
I've done hours of testing. First, with DU 15.0 from El Cap. With that, I
found that copy perfomance on "Restore" from one to another disk or
partition, as well as "New Disk Image from a partition" is optimal.
But with DU 16.0, which is part of Sierra, performance goes does
significant
> On Apr 3, 2017, at 8:56 AM, Scott Talbert wrote:
>
> It's getting a value from the getattrlist path.
>
> The fact that the data is cached at mount time is an interesting clue. It
> suggest that perhaps there may be some window just shortly after mount that
> the incorrect data is getting re
It's getting a value from the getattrlist path.
The fact that the data is cached at mount time is an interesting clue.
It suggest that perhaps there may be some window just shortly after mount
that the incorrect data is getting reported and cached.
It's a FUSE filesystem. However, some of th
