Changing the directory where Fog images are stored question

[Wayne Workman]

@PageTown It appears that 1.2.0 doesn’t have the settings that @Hanz was talking about.

You’ll have to do it manually.

You’ll need to edit /etc/exports
and you’ll need to change the web interface in storage management to reflect the new location
You’ll need to configure permissions on the new location, and you’ll need to create the subdirectory dev and the (hidden and empty) .mntcheck files.

[PageTown]

@Wayne-Workman

How do I create the .mntcheck files? Can I copy them from the default images/dev locations that was created when I did the original Fog install?

[Wayne Workman]

@PageTown You can create them like this, but substitute your new path for /images

touch /images/.mntcheck
touch /images/dev/.mntcheck

that’s it. They are literally just blank files. You don’t need to do any copying.

[PageTown]

@Wayne-Workman

I think I did everything correctly, but I am receiving this error when I try to upload an image:

[Wayne Workman]

@PageTown Check your firewall, and set 777 permissions recursively on /media/bfd/images

chmod -R 777 /media/BFD/images

[PageTown]

@Wayne-Workman

The chmod command didn’t work.

If it was a firewall issue, wouldn’t that block my being able to register the host?

[ITSolutions]

@PageTown d you run chmod as sudo?

sudo chmod -R 777 /media/BFD/images

[Wayne Workman]

@PageTown said:

The chmod command didn’t work.

It might not have solved the issue, but I promise it’s a necessary step.

You’re /etc/exports should look like this:

/media/BFD/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/media/BFD/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

You’re .mntcheck file creation would be:

touch /media/BFD/images/.mntcheck
touch /media/BFD/images/dev/.mntcheck

Then to recursively set that directory and the mntcheck files permissions:
chmod -R 777 /media/BFD/images

You’d need to reset the nfs and rpc service next (or just reboot).

sudo service nfs-kernel-server restart
sudo service rpcbind restart

Seeing how you have an NFS related issue with uploading, you might want to look through this wiki and try some of these things manually:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_NFS

[PageTown]

@ITSolutions

Yes.

[Sebastian Roth]

@PageTown So what error did you see when trying to chmod?? We need information to be able to help!

[PageTown]

@Sebastian-Roth

There was no message when I ran the chmod command. It looked to me like it took it, but I am still getting the same error that is in the screen shot I posted when I try to pull an image.

[Wayne Workman]

@PageTown There has to be something wrong somewhere. Can you take more pictures of the upload process? A lot of information is displayed during the upload and that would help us solve this. Also, can you give us a screen shot of your storage node settings area? What is your FOG Server’s IP address?

[Sebastian Roth]

@PageTown The path /media/BFD sounds a bit like this is an external drive mounted into that path. What filesystem is on that drive? Run mount | grep media to check and post the output here in the forums.

[PageTown]

@Sebastian-Roth

I have Ubuntu and Fog installed on a 120GB SSD. I am trying to save my images to a separate 1TB HDD drive. The 1TB drive is an internal drive, connected to the mother board via SATA.

The filesystem is NTFS. See screenshot.

The result of running the mount | grep was : /dev/sdb1 on /media/BFD type fuseblk (rw, nosuld,nodev,allow_other,default_permissions,blksize=4096)

[Sebastian Roth]

I am not sure if NFS on a NTFS partition is a good idea? Anyone ever tried this? I haven’t so far. Permission issue might be because of this but I am not sure.

[ITSolutions]

@PageTown You don’t want to use NTFS on an NFS share. It is best if you reformat the drive to Ext4 and then go back through the steps outlined by @Wayne-Workman

[pugnacious]

@Sebastian-Roth I never got it to work at all. I ended up swapping to a different solution.

[PageTown]

@Wayne-Workman

Ok, I am up and running! I was following your instructions regarding the exports file and creating the mntcheck files and went into my BFD drive to look at the /images and /images/dev folder when I right clicked on a folder and noticed that the path was not BFD but BFD_. I renamed the path in exports and in storage management and it started pulling an image from my test machine.

I feel foolish that it was something so simple, but I don’t recall naming the drive with an underscore. The only place the additional underscore even shows up is when you right click on a file or folder on it and look at the path.

Thanks everyone for your time and patience!

[Wayne Workman]

@Sebastian-Roth said:

I am not sure if NFS on a NTFS partition is a good idea? Anyone ever tried this? I haven’t so far. Permission issue might be because of this but I am not sure.

This might have been the issue all along for those that have attempted storage nodes on Windows Servers.

I’m sure the permissions can be sorted out though for NTFS. I suppose you’d set the permissions to “everyone” for full control.

[pugnacious]

@Wayne-Workman
The issue i was having with windows storage nodes is likely a permissions issue, but the first thing we tried was setting the permissions across the board to full control. Good luck figuring it out. It was so annoying, we swapped the storage node for a linux machine.