On 2010-10-08 18:58 +0200, Xavier Bestel wrote:
> On Fri, 2010-10-08 at 18:45 +0200, Sven Joachim wrote:
>> Interesting, chown(2) does not mention EINVAL as a possible error code.
>> I'm not familiar with cifs, can you chown other files on the remote
>> drive?
>
> No, I can't chown anything on the drive.
> I don't really know why that is. The underlying filesystem (it's on a
> D-Link DNS-323, a small linux appliance) is ext3, so it supports
> uids/gids. Albeit the SMB user isn't administrator on the machine, so I
> guess that's why it can't chown.
That sounds plausible.
> I changed the BM_REPOSITORY_SECURE option to "false" to avoid BM doing
> the chown, and now it should work. I'll wait for the crontab to fire
> tonight, and for the backup to complete (>24h) to check.
Setting BM_REPOSITORY_SECURE to false should do the trick, please report
back whether the backup succeeds.
Thanks,
Sven
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
