BIT fails to create hardlink on locally mounted NFS drive

[Simone Gaiarin]

I have a remote drive locally mounted through NFS as a destination for my backups.
From the log I can see that the command "cp -aRl ...." fails with code 256 , so it seems it cannot create hard links in the target folder. Indeed it takes a huge amount of time to perform the backup.
Creating an hard link manually on the drive works.

How can I solve this?

[Germar (germar)]

Doesn't need to be hard links which will fail that command. Could be permissions or corrupt files, too.

Please copy the 'cp -aRl' command, manually create the 'new_snapshot' folder and run the command manually from Terminal. This should show the exact error.

BTW backing up to a mounted share is very inefficient. Rather use BackInTimes SSH mode.

[Simone Gaiarin (simgunz)]

You are right. Indeed the error I got is "operation not permitted". Probably there is something messed up with the NAS configuration.

The current permissions are:
-r--r--r-- 1 nobody users

What kind of permission do you need to create the hard link?

If I execute:
touch a && cp -l a b

it works on the drive but it doesn't work within a snapshot folder.

[Germar (germar)]

The destination folder would need at least rwx (0700). But thats not a permission problem. Permission problems would raise 'Permission denied' error.

Do you run BackInTime as regular user and are there files inside the last snapshot which are not owned by you? Check this out:
find ./ ! -user "$(whoami)" -ls

[Simone Gaiarin (simgunz)]

When I write I file on that drive the user is set to nobody (NFS does this for some reason), but that doesn't coincide with my local user indeed.