I tried a couple of backups to Minios (running on a Windows 2012 R2 server), and at some point the Mac kernel panics. This happened twice (I only have the most recent kernel panic details). This is on a Mac mini that has been ROCK SOLID until now (it’s the first time I’ve ever seen a kernel panic on a Mac).
FWIW I’ve been running restic at the add-cache branch (commit 60538650), which is beyond the 0.7.3 release, and it works fine. But I’m using the SFTP backend, in case it has anything to do with that.
Hi, I haven’t had a chance to sit down and collate all the info for creating the issue in GitHub.
As far as cooling is concerned, I never heard the fan kick in (it always runs, but very quietly), which I have heard previously (e.g. when setting up macOS initially, when it does a full index of everything).
I was testing against Minio, so I’ll do another test against an external USB3 disk to see if that is any different. I must admit I’m pretty frustrated with my Restic testing so far… (especially because when it works it is amazing).
I’ll create an issue in the Go repository, let’s see if they have any idea what’s going on here. No user-space program should be able to crash the kernel…
I would tend to suspect bad RAM or similar hardware problem if it happens under load. Can you run a hardware test?
I had a Macbook that was solid for 2 years and then suddenly started having random panics. The built-in hardware test showed a problem with the disk. Apple replaced the logic board & SSD, and it’s been solid ever since.
I will run one this evening. Does restic use an enormous amount of RAM? I’m not a super heavy computer user, but I routinely have 20-30 Safari tabs open, with 5-10 other apps running simultaneously (i.e. what I would consider fairly typical computer use).
I successfully ran a backup of the same source to an external USB 3 drive. So could there be a bug in the Minio implementation?
It happened twice, so it seems reproducible. It didn’t kernel panic when backing up to the external USB 3 drive, do you think there’s a big difference in memory utilisation (to justify the explanation of faulty memory) when going to Minio rather than a local disk?
There was a bug in the s3 backend using a lot of RAM, that was resolved but is not contained in a released version of restic yet (see #1267), that could be it. The description of the issue is here #1256.
Hi, sorry for the slow progress. I suspect @armhold might be right. Both the Apple Hardware Test and memtest86 cause the machine to freeze at some point (AHT froze at around 11 minutes, memtest86 after almost two hours), so I need to do further testing by removing each of the memory DIMMs and testing individually.
In 30 years of using computers and working in IT, it’s the first time I’ve seen a hardware problem (still just an assumption) that is this subtle. Further testing to be done, and a further update also. If I can narrow it down to a single DIMM, I will re-check restic 0.7.3 against Minio to see if I can make it fail again. (I will also test the binary @fd0 has given me, but I suspect that will be much quicker, therefore less likely to trigger the kernel panic).
Just to make things a little more complicated, in the meantime I’ve also upgraded to High Sierra. =)
I’m sorry to say that I’m glad to hear that. It’s not the first time restic uncovered a hardware problem… I’ve closed the issue for the Go project over at GitHub.