I've been using FFS 11.3 ARM version since it came out. I've been waiting to fully tested this before posting here but I'm afraid something in the app is triggering kernel panics on macOS. I must have 10 to 15 crash logs by now.
After several attempts using different scenarios, my findings are:
- using SMB to SMB transfers
- using local to local (onedrive folder)
- using local to SMB
- using SMB to external hard drives
- using external hdd to ext hdd
Pretty much in all of them it reboots.
Being plug in to charger or not, having a dongle attached to it or not, having an external monitor or not, having only freefilesync running in the background or not, every single time I try to sync to folders with more than 50GB of data it crash and I get a reboot.
I use stats to monitor all the data and I've noticed that CPU is about 9%~15%, RAM 58~80%, and SSD is pretty much empty, 19% full. So the system is not even being crushed.
I can't say what is causing it. When I was in donation period I used to mess around the parallels syncing but not anymore. I'm using the default only 1. It went as far as fresh install without the system configurations and didn't succeed.
I don't know if there are a lot of people out there using this on m1 and syncing this amount of data but I have multiple folders that can hold more than 500GB and I need an app that I can use to sync everyday.
I love the FreeFileSync UI and it has been my preference since I used windows. Great job doing this app BTW. I hope someone can figure it out what is causing this.
All the best
FreeFileSync 11.3 - crashing - kernel panics - reboot - huge data
- Posts: 9
- Joined: 29 Jun 2021
- Posts: 9
- Joined: 29 Jun 2021
UPDATE: If anymore else find this and are facing the same issue. This is now a known issue for Big Sur and SMB protocol. The workaround solutions are as follows:
a) Change the communication protocol to AFP
PRO: easier if you have already the volume all set
CONS: it's slower than SMB 3.1
b) Create a blank disk from disk utility - you can either choose a Read/ Write or a Sparse
PRO: it's faster than AFP + if you create a sparse of let's say 1TB, you can change all you have in the AFP/SMB volumes because the space will only grown after you start copying files (there's no need to move them to external ssd and move them back to NAS volume)
CONS: You can only mount one dmg per user
c) run a rsync script with automator
PRO: might be faster if you use the update block feature
CONS: it hasn't the UI and all the features that make FFS so good
It's never enough to stress this, nothing wrong with FFS 11.14.
a) Change the communication protocol to AFP
PRO: easier if you have already the volume all set
CONS: it's slower than SMB 3.1
b) Create a blank disk from disk utility - you can either choose a Read/ Write or a Sparse
PRO: it's faster than AFP + if you create a sparse of let's say 1TB, you can change all you have in the AFP/SMB volumes because the space will only grown after you start copying files (there's no need to move them to external ssd and move them back to NAS volume)
CONS: You can only mount one dmg per user
c) run a rsync script with automator
PRO: might be faster if you use the update block feature
CONS: it hasn't the UI and all the features that make FFS so good
It's never enough to stress this, nothing wrong with FFS 11.14.
