Freaky behaviour or is it ext3 fault?

[smartstradamus]

I converted an ntfs partition with about 400gb of movies and software to ext3 which went without a hitch. I proceeded to remount the partition to /var/hda/files/drives/drive1 which is where all my shares are and all my downloading app save files.
My shares worked fine and my sabnzbd and sick beard worked fine until I realised that sabnzbd and sickbeard had started creating the newly downloaded files with permissions that stopped me from accessing the new files.
Sabnzbd would create files/folders with apache as the owner and nobody else was allowed access. Sickbeard would create files/folders with root as the owner and nobody else was allowed access.
This was frustrating because I only changed the partition to ext3 so that dlna would autoscan the drive and update the dlna share.

Lastnight I did a fresh install of amahi and mounted the drive in usual place and installed sabnzbd and setup my shares but it is doing the exact same thing.
Previously I was using my amahi with sab and sickbeard for almost a month without problem.
All I can think of is that the change to ext3 is the root of this problem.

Can anybody help me out with this one?
I'm at a loss and my amahi is useless for me until I can figure this out.


Thanks

[moredruid]

on ext3 you will need to set the correct permissions on the shares. You didn't have this issue on NTFS because Linux doesn't care about NTFS permissions (it doesn't see them) and is able to read/write. Usually having the group "users" own the top directory (or mount point) solves a lot of issues.

[smartstradamus]

I've tried that I think.
From root I set owner to my user and group to user
Both have create and delete but it won't let me change the read/write option below them.
It still creates a folder owned by root or apache when new files are downloaded.
I know I can change the sabsettings to use chmod 777 when creating new files but this still leaves me a bit stuck when using

Edit:
Solved,after a re-install.