[fog] Unable to move image files via FTP

[arives]

Hello,

 

I recently finished installing and configuring a fog server for our Auto Auction. It will service around 80 hosts.

 

We have an Iomega Storcenter PX4 300r NAS. The Nas supports NFS and FTP protocols.

When uploading an image from a host, everything goes fine until the last 1%, and then it errors saying it is unable to move from /mnt/pools/A/A0/fog/dev to /mnt/pools/A/A0/fog.

 

If I manually rename and move the files, everything works fine and I can deploy the images.

 

From what I gather it is a permissions issue, but when I use filezilla to connect to my nas the directories all show permissions set to 777. The newly written image file in the dev folder has different permissions 644.

Is there a fog setting or file that I can edit to change the permissions for this file? I know I'm kind of reaching but it's all I can come up with...

 

I'm kind of lost as how to proceed to resolve this issue...

 

Thanks in advance for any help.

 

Adam

[morganw]

I think you would have to look for a umask setting on the NAS box, or look to try and match the owners id number with the id number for the FOG user on the server.

[arives]

As far as a umask setting goes, I don't have that option. I am a beginner in Linux could you give me an idea how to find these resource ID's?

[morganw]

On your fog server you can look at /etc/passwd to see the user ID:

Understanding /etc/passwd File Format

Hopefully on your NAS box you can set the ownership of the relevant directories with this ID number.

[arives]

Yeah I cannot execute a chown when I connect to my NAS via FTP. It's an unrecognized command. Edited March 23, 2012 by arives

[morganw]

You can't use chown over FTP, you would have to set ownership and permissions through some other method. If it was a server you would do it through the shell, I would have thought your NAS box would have some kind of web interface to let you configure things like this. If your NAS supports iSCSI you could use this instead and it should be easier to configure the permissions as it's seen as local storage by the server. Or getting more complicated, you could virtualise the FOG server and use NFS for the VM storage. To be honest though you could use any old workstation as a storage node if the hard disk is big enough, just queue unicast deployments and everything will still be pretty quick.