How to create subfolders in a storage node
-
@george1421 Well I have sad news, it worked for me.
All I did was create a directory under /images (called vol1). The path was /images/vol1 I did change the owner to
fog.root
Then I setup a new image and set the path to vol1/WIn7Test and then assigned that image to a virtual box VM I have. It captured the image correctly and moved it to the /images/vol1/Win7Test directory correctly. -
@george1421 is your vol1 a directory in the /images or a separate hard drive. Mine is a separate hard drive /dev/sdb mounted to /images/vol1 when i made a directory, your right it did work fine. just not a directory mounted
-
@sdm42doc Yes it was a directory, but that should work the same as the mount point for a hard drive.
Are the permissions set correctly on that mount point after its mounted?
-
@sdm42doc We can test without imaging easy
Mount up that new drive to the vol1 mount point under /images
Then from an external computer ftp to the fog server using the user ID and password that is defined in the /opt/fog/.fogsettings file.
Navigate to the /images/vol1 directory and make a directory using the ftp client (like from a ms windows box). If you can make the directory then imaging should work. That is what the FOS engine does. It captures the image to /images/dev/<mac_address> then when done it moves the files using FTP to /images/<image_name>
-
@george1421 I believe I have the rights correct, as attached, maybe you will see something I missed. I appreciate all your help!
-
@sdm42doc you have them correct. Did you try with the external ftp client yet?
I’d like to duplicate this with my home lab, but my esxi server is down with a failed power supply (one is on its way from amazon). All I have right now is my FOG-Pi server so I can’t really add a second drive to that to duplicate what you are seeing.
-
@george1421 I can walk around and upload files from my desktop, create directories, ect all through that HD marked vol1 logged in as fog through ftp.
-
@sdm42doc (thinking out loud) Yet imaging fails with the error screens you posted…
FTP works, can navigate to, can create directories
permissions are set correctly
captured images going to /images/dev/<mac_name> but not being moved to /images/vol1/<image_name>
Using Ubuntu 16.04.02 with current version of FOG 1.4.0
Works with /images/vol1 as a directory not as mounted volume
== should be working
… -
@george1421 this is one of those weeks, my testing was as follows
1> physical hardware rack fog server with raid controller mirror raid with volumes / and /vol1 ubuntu 16.04.02 fog 1.4.0
2> esxi hosted fog server with two volumes / and /vol1 ubuntu 16.04.02 fog 1.4.0tomorrow, I am going to do a fresh install on esxi, and test it accordingly and try to triplicate it and I will report back.
-
@sdm42doc Are you getting the same error as in this post with your home kit where you didn’t try to setup the storage node bits?
https://forums.fogproject.org/topic/9456/how-to-create-subfolders-in-a-storage-node/19I can/will also duplicate with our dev lab at the office tomorrow. I can more closely emulate what you have with that environment.
-
@sdm42doc selinux is disabled on these servers, right? or at least set to permissive. I would think you would have had other issues if selinux was stepping on things.
-
I need to rethink things.
That said, however, you shouldn’t need to export the new mount point. -
@Tom-Elliott @george1421 - Here is the latest news.
I removed the mount points on the server in /etc/exports
so they only showI uploaded an image to /images/vol1/… (and it looks successful
However, after looking into the restart on the server, the image file copies the name only with 0 kb.
Then after the temp files remain in /images/dev/macaddress, ect. and don’t move.
Now, I am confirming that a “directory” outside of a directory volume in /images/sample do work properly. Where as /images/sample is the directory with the proper rights.
Image is complete and computer restarts
Then the image is moved correctly into the directory /images/sample
My other thoughts are that I may try. Is it an ext4 thing or should I go back to ext3, and try it.
Let me know know what you think. I am willing to work with you guys for the success of this project as always! Thank you