Re: FreeBSD+samba as a time machine server for OSX/Sonoma?

On 9/8/24 04:48, David Chisnall wrote:
> If I mount the same share, I can reproduce this:
> 
> $ mkdir tmp
> $ touch tmp/foo
> $ mv tmp fmp
> mv: rename tmp to fmp: Operation not supported
> 
> So it appears that something in the FreeBSD port of Samba has broken the 
> ability to rename directories.

Nice catch.

I installed 4.16 on a spare system and setup a test share. I'm able to 
reproduce your "Operation not supported" test. But I also see that (from 
the mac) I get the same error if I try to remove tmp/foo! I'll add some 
info to your PR.

On 9/7/24 02:51, Mark Delany wrote:
 > I'm going to ask a silly question here. But why are people running 
samba instead of
 > netatalk if they are only using the timemachine backup capability?

In my case when I upgraded to big sur (2021) it looked like netatalk3 no 
longer worked; my local osx expert thought that apple had phased out afp 
support so I switched to samba413.

It wasn't until much later that I figured out when you make changes you 
pretty much need to nuke your old backup and start over. And also delete 
and recreate the share config on the mac. So maybe if I had just done 
those things when I upgraded to big sur I would have continued to use 
netatalk3.

But last year I got a brother multi-function printer and it was pretty 
easy to create a samba share that the printer can store scans to. That's 
been pretty handy so I'm likely to keep samba.

On 9/8/24 05:29, Dimitry Andric wrote:
 > I have never needed to explicitly set fruit:posix_rename, my Time
 > Machine backups work completely fine without it (maybe it defaults to on
 > now?). I have been using Samba 4.19 since the port came out too.

Right, fruit:posix_rename defaults to "yes" (see man vfs_fruit).

		Craig