[Borgbackup] Borg on Mac with Fusion Drive

[Stefan Buehler]

Dear Thomas,

thanks for the explanations and for the bug fix. Even if it was just the info output that was wrong, it really is useful to see which files are truly new.

All the best, and keep up the good borg work

Stefan

> On 26. Feb 2018, at 10:05, Thomas Waldmann <tw at waldmann-edv.de> wrote:
> 
> 
>> I’m running borg backups on a Mac that has a “fusion drive”. (A combination of SSD and spinning disk.)
>> What puzzles me is that I never see file status “M” in the log output,
> See one of my previous posts from today. It's a (cosmetic) bug.
> 
> 
>> and also there seem to always be a lot of (seemingly random) old files being added again.
> 
> That might be covered by the FAQ already:
> 
> http://borgbackup.readthedocs.io/en/stable/faq.html#i-am-seeing-a-added-status-for-an-unchanged-file
> 
> 
>> Is it possible that this behaviour is related to the fusion drive?
> 
> No.
> 
> At least not if the hardware is working as expected (which means that it
> looks like any other block storage device and the optimization of the
> slow hdd using the fast flash memory is fully transparent to the user).
> 
> Borg usually does not even talk to the block storage device directly,
> borg just uses filesystem calls.
> 
> Exception is when you use --read-special and directly read from
> /dev/thatblockdevice, then borg reads blocks directly from that device
> (via the kernel, so nothing unusual here either).
> 
> 
>> I’m running with the defaults for the --files-cache variable, should I use something else there?
> 
> No, the defaults are usually fine (and safe).
> 
> 
> -- 
> 
> GPG ID: 9F88FB52FAF7B393
> GPG FP: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393
> 
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup