shypike wrote:Samba results are unpredictable, that's the whole issue.
There have been twenty something releases since 0.5.0 and a huge amount of changes.
As far as SABnzbd is concerned, it expects the file system to behave like a normal native file system.
In fact SABnzbd doesn't really bother with access rights on admin and incomplete folders,
it just uses defaults.
Only for "complete" will it set explicit access rights, if so instructed.
I'd expect this to work too. I cannot understand what Sab is doing differently. Perhaps its the 'binary' flag (for windows).
Do you run under a "special" account that has different rights?
as you can see in the log, nope; its running as root (set to root in the defaults-file).
Can you create the failing files from a terminal session on the Linux box?
Like: /mnt/sharedoos/news/incomplete/Californication - 5x06 - Love Song/__ADMIN__/SABnzbd_nzf_lKRBDo
yes. And if I do that, it'll try to create 'Californication - 5x06 - Love Song.1' which will fail for the same reason. This tells me it, indeed, does have access to the filesystem, yet does not want to/cannot write.
It's bizarre a directory with -exactly- the same rights (and remember, samba is a thing the kernel has to think about, not userland apps; its all overlaid in a posix compliant sauce) that isnt a mount works fine, and when you mount your sambadevice in it, with proper access rights, it fails.