Changing the directory where Fog images are stored question
-
@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 mediato check and post the output here in the forums. -
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)
-
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.
-
@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
-
@Sebastian-Roth I never got it to work at all. I ended up swapping to a different solution.
-
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!
-
@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.
-
@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.