• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

How to create subfolders in a storage node

Scheduled Pinned Locked Moved Solved
General
5
36
9.6k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T
    Tom Elliott @Hongyun
    last edited by Feb 15, 2017, 7:11 PM

    @Hongyun Yes, update please. I fixed the stripping of forward slashes, and I think backslashes too.

    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

    Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

    Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

    H 1 Reply Last reply Feb 15, 2017, 10:00 PM Reply Quote 0
    • H
      Hongyun @Tom Elliott
      last edited by Feb 15, 2017, 10:00 PM

      @Tom-Elliott Can you let me know where to download 1.3.5? I got a version by using git clone command, but the version I downloaded still have the same problem.

      git clone https://github.com/fogproject/fogproject.git

      G 1 Reply Last reply Feb 15, 2017, 11:01 PM Reply Quote 0
      • G
        george1421 Moderator @Hongyun
        last edited by george1421 Feb 15, 2017, 5:07 PM Feb 15, 2017, 11:01 PM

        @Hongyun FWIW: 1.3.5 has not been released just yet.

        If you would like to update to the latest release candidate 1.3.5-RC7 (that will most likely become 1.3.5 stable) you can follow these steps:

        git clone https://github.com/fogproject/fogproject.git
        cd fogproject
        git checkout dev-branch
        cd bin
        ./installfog.sh -y
        

        Understand that will tell git to only look at the dev-branch. So once 1.3.5 stable is released you will want to run these commands to reset git back to the main feed:

        cd fogproject
        git checkout master
        cd bin
        ./installfog.sh -y
        

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        H 1 Reply Last reply Feb 15, 2017, 11:19 PM Reply Quote 1
        • H
          Hongyun @george1421
          last edited by Feb 15, 2017, 11:19 PM

          @george1421 Thanks! I will wait for the stable release then, it’s not super urgent 🙂

          G 1 Reply Last reply Feb 15, 2017, 11:21 PM Reply Quote 0
          • G
            george1421 Moderator @Hongyun
            last edited by Feb 15, 2017, 11:21 PM

            @Hongyun There is no harm in doing this now or waiting for the stable release. The choice is yours.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            H 1 Reply Last reply Feb 17, 2017, 5:17 PM Reply Quote 0
            • H
              Hongyun @george1421
              last edited by Feb 17, 2017, 5:17 PM

              @george1421 Thanks! I just upgraded FOG, and it works perfectly 🙂

              1 Reply Last reply Reply Quote 1
              • S
                sdm42doc
                last edited by May 24, 2017, 6:00 PM

                Has anyone had any luck with directories under /images.

                I mounted another volume (for more storage) under /images to try to force it and no luck.

                I thought you could have multiple storage nodes on the same server with additional hard drives at one point. I have been a “fog user” since the beginning, and thought for sure i had this setup before.

                I am on Ubuntu 16.04.02 with current version of FOG 1.4.0.

                G 1 Reply Last reply May 24, 2017, 6:23 PM Reply Quote 0
                • G
                  george1421 Moderator @sdm42doc
                  last edited by May 24, 2017, 6:23 PM

                  @sdm42doc No joy for you, subfolders are still not supported.

                  Now you do have some options.

                  1. If your server uses LVM, just add the additional space to the LVM volume where the /images are.
                  2. Temp mount the new volume over another directory, move the contents of /images to the new volume via the mount point, disconnect the mount point and mount it over /images

                  There are some other ways to extend it but it then gets a bit messy.

                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                  1 Reply Last reply Reply Quote 0
                  • G
                    george1421 Moderator
                    last edited by george1421 May 24, 2017, 1:21 PM May 24, 2017, 7:19 PM

                    Just circling back on this after I talked with the developers. That sub directory functionality WAS added to FOG 1.4.0. I was wrong before. You can create subfolders in the /images directory something (as seen below). Once you set your image name you can alter the image path field. Understand there is ONE caveat here, as in my example the /images/myfolder directory MUST exist before you create this image definition. If not your capture will fail.

                    In your case the /images/myfolder (or what ever you call it) will be a mount point for your new disk volume.

                    0_1495653475052_fog_subfolders.png

                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                    S 1 Reply Last reply May 24, 2017, 7:35 PM Reply Quote 0
                    • S
                      sdm42doc @george1421
                      last edited by May 24, 2017, 7:35 PM

                      @george1421 Thank you. I actually got the subfolders to work. I had to manually create the folder, set rights, and it works inside /images. However, my latest thoughts, I want to add hard drive space outside of LVM to /images. So I set a mount point with the proper rights to /images/vol1, vol1 being the new mount point of a hard drive. The image looks like it goes up no issues, until the end, the system won’t copy the images from /dev over to /vol1. I tried creating this as a storage group /images/vol1, and a fake directory if you will concept and I have no luck. In the past, couldn’t you have more HD in the server for storage nodes, or am I dreaming about this. I have spent two days, trying to figure this out, its now a challenge to see if it works. Take care, thank you for the response.

                      G 1 Reply Last reply May 24, 2017, 9:14 PM Reply Quote 0
                      • G
                        george1421 Moderator @sdm42doc
                        last edited by May 24, 2017, 9:14 PM

                        @sdm42doc Just for clarity what I posted below didn’t work for your setup?

                        If not can you provide the output of these commands

                        1. df -h
                        2. showmount -e 127.0.0.1

                        I talked with the developers for quite a while and they were positive it would work as I outlined.

                        If you setup a storage node route, you need to duplicate the /images base structure below on the new volume. I won’t probably have time tonight to test this in my dev environment but I will get to it tomorrow night.

                        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                        S 1 Reply Last reply May 24, 2017, 10:31 PM Reply Quote 0
                        • S
                          sdm42doc @george1421
                          last edited by May 24, 2017, 10:31 PM

                          @george1421 attached is the screen shot from the fog box.

                          0_1495664599577_Screen Shot 2017-05-24 at 6.21.05 PM.png

                          I also replicated all of the interiors of the files as outlined, copying the /dev/ files to the vol1/ ect.

                          On upload, it looks like all is well, the image is going to /images/dev/(mac address of machine) then on the final write, it fails, as attached.

                          I am going to try to recreate this issue in my home lab tonight.

                          0_1495665048302_IMG_1599.JPG

                          0_1495665060371_IMG_1600.JPG

                          G 1 Reply Last reply May 24, 2017, 10:42 PM Reply Quote 0
                          • G
                            george1421 Moderator @sdm42doc
                            last edited by May 24, 2017, 10:42 PM

                            @sdm42doc This looks like you might have a storage node configuration still in place. If you look at your last image its using the /image as the root, but the error messages in the next from the bottom its trying to move the file from /images/vol1/dev (but the image is in /images/dev).

                            The first picture shows that you have the right shares in place for the secondary nodes.

                            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                            1 Reply Last reply Reply Quote 0
                            • Wayne WorkmanW
                              Wayne Workman
                              last edited by May 24, 2017, 11:25 PM

                              I didn’t read the whole thread, just the title. Another guy tried doing this but it ended up not working, I told him to undo it.

                              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                              Daily Clean Installation Results:
                              https://fogtesting.fogproject.us/
                              FOG Reporting:
                              https://fog-external-reporting-results.fogproject.us/

                              1 Reply Last reply Reply Quote 0
                              • S
                                sdm42doc
                                last edited by May 25, 2017, 12:09 AM

                                So I tried it on my home lab, and have no good results. I don’t think it is going to work.

                                The uploads go up to /images/dev then only move the image name with 0MB to the /images/vol1/ folder, the other files stay in /images/dev/0050569fb7e7 d1p1.img, ect. but it looks like the image completed with no errors.

                                0_1495670861881_Screen Shot 2017-05-24 at 7.46.37 PM.png

                                0_1495670944373_Screen Shot 2017-05-24 at 8.08.46 PM.png

                                G 1 Reply Last reply May 25, 2017, 12:18 AM Reply Quote 0
                                • G
                                  george1421 Moderator @sdm42doc
                                  last edited by george1421 May 24, 2017, 6:19 PM May 25, 2017, 12:18 AM

                                  @sdm42doc

                                  So I tried it on my home lab, and have no good results. I don’t think it is going to work.

                                  If we can trap the error we can get it fixed, so don’t give up hope on this.

                                  Just for clarity you created the vol1 in images before you imaged the computer? (this is was a sticking point during my discussion with the devs). I’ve got 1.4.0 setup in my home lab, let me see if I can duplicate your results.

                                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                                  G 1 Reply Last reply May 25, 2017, 12:37 AM Reply Quote 0
                                  • G
                                    george1421 Moderator @george1421
                                    last edited by May 25, 2017, 12:37 AM

                                    @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.

                                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                                    S 1 Reply Last reply May 25, 2017, 12:43 AM Reply Quote 0
                                    • S
                                      sdm42doc @george1421
                                      last edited by May 25, 2017, 12:43 AM

                                      @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

                                      G 2 Replies Last reply May 25, 2017, 12:56 AM Reply Quote 0
                                      • G
                                        george1421 Moderator @sdm42doc
                                        last edited by May 25, 2017, 12:56 AM

                                        @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?

                                        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                                        1 Reply Last reply Reply Quote 0
                                        • G
                                          george1421 Moderator @sdm42doc
                                          last edited by george1421 May 24, 2017, 7:02 PM May 25, 2017, 1:01 AM

                                          @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>

                                          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                                          S 2 Replies Last reply May 25, 2017, 1:04 AM Reply Quote 0
                                          • 1
                                          • 2
                                          • 1 / 2
                                          • First post
                                            Last post

                                          158

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project