timeisweird

@JorgeB Do we need to submit a ticket to Limetech so this can be patched?

I commented out "smb3 directory leases = no" and made it persistent with a copy command in the /boot/config/go file. Unfortunately it does not solve the Time Machine error. For what it's worth I also tried without using Time Machine encryption and that also made no difference. Seeing as I'm still testing Unraid and don't have any important data on my pool, I'm tempted to try with the drives configured in an array again but on 7.2.1. Although I really wanted to make use of zfs.

I'm running MacOS Sonoma 14.3 (23D56). A few weeks ago I was testing Unraid with my 4x HDDs in xfs in an array. I had no issues with the SMB Time Machine then. The problem has appeared since switching the setup to a zfs pool or possibly due to upgrading from Unraid 7.1.4 to 7.2. Looking at the release notes for 7.2 it does mention changes to the SMB config: I might try to revert this and see if it helps.

Hello, I am busy testing Unraid, so far I really like the software however I am unable to get Time Machine to work. I have 4x 4TB HDD's running in a raidz1 pool. I am running Unraid 7.2 andI create the SMB share as follows: minimum space: 1 KB primary storage: name of the zfs raidz1 pool secondary storage: None export: Yes / Time Machine time machine volume size limit: 2048000 MB case-sensitive names: Auto security: Private relevant user has read/write access I am able to mount the share as a Time Machine volume on my Mac (Sonoma 14.3). I specify to encrypt the backup and set a disk usage limit of 2.0 TB (also tried 1.9 TB to be sure it was less than time machine volume size limit). When it comes time to backup I get the error that the backup disk image could not be created. Specific text of the error: "The backup disk image could not be created". I have tried many times, restarted both machines and tried re-creating / re-adding the share. Where am I going wrong?