[OS X] Cannot create download directory

[shypike]

It's OSX that handles this badly.

[Stitch]

That's understandable, I know where your coming from..

We can't do anything about OS X though I guess. Sabnzbd is the one that's creating the phantom drive, rather than waiting for the real drive to be attached isn't it? Would a toggle be worth your development time ? I don't know

[shypike]

Mounts are transparent. OSX doesn't really tell whether or not there's
a drive attached.
There are some tricks we could do, but they remain tricks and may not
be reliable across systems.
It's under investigation.

[Stitch]

I see, thanks for increasing my understanding! I will keep doing the manual unmount.

[yuiop88]

Mounts are transparent. OSX doesn't really tell whether or not there's
a drive attached.
There are some tricks we could do, but they remain tricks and may not
be reliable across systems.
It's under investigation.

I also have this problem. I use a NAS to store Sabnzb's downloads, but when it isn't connected for some reason, Sab creates a folder with the mounted servers name in /Volumes.

Isn't it possible to just add a setting to the configuration option to disable the automatic creation of folders when they aren't present? That would solve our problems and when it's a setting other people can leave it the way it is now.

[shypike]

What do you suggest SABnzbd does when it cannot create a folder?

[JamieM]

I'd suggest pause everything and notify the user in the interface and maybe even via growl

[SynePDX]

I have a similar problem in Windows 7 using 0.6.8. I had hoped this latest release would correct the issue, but it didn't.

I set SAB to dump to a drive mapped to a non password protected WD Live Hub. I have tried using both the mapped path and the UNC.

This all worked fine, via mapped drive, up until one day SAB started throwing errors in the logs that it could not create the destination folder, even though that folder existed, had existed previously. And SAB was dumping files into the folder, even while it threw errors that it couldn't create the folder it was dumping files into. I haven't been able to tie the event to anything specific.

It does this all the time now. My log is always full of "Cannot create directory H:\NEW". It could be a problem with the WD, but I agree with the poster suggesting a way to disable the auto-create feature. Leave it by default and just add a check or radio to disable the autocreate function, since you can't control the behavior of the destination device and SAB doesn't have the error handling to cope with whatever is going on. Then again if it isn't happening to many people, I guess just leave it.

Dunno.

[shypike]

I understand that this an issue for you.
But SABnzbd only attempts to create a folder if it doesn't already exist.
For some reason it gets the message from the OS that the folder doesn't exist
and subsequently that it cannot be created either.
How is it supposed to understand that it's alright to continue?
I suppose by trying to create sub folders anyway, but that's rather an odd way
to work around issue in the OS, isn't it?

[SynePDX]

I understand that this an issue for you.
But SABnzbd only attempts to create a folder if it doesn't already exist.
For some reason it gets the message from the OS that the folder doesn't exist
and subsequently that it cannot be created either.
How is it supposed to understand that it's alright to continue?
I suppose by trying to create sub folders anyway, but that's rather an odd way
to work around issue in the OS, isn't it?

Dunno dude. It manages to stumble past the problem and write the data to the folder that it doesn't know exists and can't create. All I know is I have a lot of shit that writes to remote file systems over SMB and this is the only thing that I have had an issue with like this. It isn't a world ending problem or a major pain in my ass. Just giving some feedback. Do with it as you will. The product rocks in sooo many other ways.