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

AWS EFS Centos

Scheduled Pinned Locked Moved Solved
Linux Problems
3
9
1.0k
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.
  • S
    spidajon
    last edited by Aug 7, 2019, 7:12 PM

    My FOG version currently is 1.5.5 and works perfectly fine. However I have attached an AWS EFS on my CentOS Linux release 7.6.1810 (Core) FOG server and able to cd into it fine. I am trying to change the default directory /images to this EFS lets call it /efs-aws and store all the images that were on /images on this /efs-aws directory.

    1. Things I have done so far is change the settings on the FOG web interface under storage to 2 tabs the “image path” and “FTP path” to /efs-aws.

    2. Change the settings under “/opt/fog/.fogsettings”. Specifically these 2 lines.
      storageLocation=‘/efs-aws’
      #storageLocation=‘/images’

    3. At first one log I saw from /var/log/messages is this

    • list itemfog rpc.mountd[8724]: Cannot export /efs-aws, possibly unsupported filesystem or fsid= required
    1. But puzzling part of this log I saw was after I put the directory “/efs-aw” in “/etc/exports”. All I did here is replace “/images” with “/efs-aws”

    /efs-aws *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
    /efs-aws/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

    I get this error below

    • list itemlist itemfog rpc.mountd[13107]: refused mount request from 10.3.4.86 for /efs-aws (/): not exported
    1. when I try to image to a test laptop I get this picture (note I just copied and pasted this picture from another forum in FOG but this is exactly what kind of error I get).
      72a5d19a-055c-4861-9c6e-9b3e5f80d4d0-image.png

    if anyone has ever tried using EFS to store all images I’d appreciate the help!

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by Aug 7, 2019, 8:56 PM

      You are at a point of trying to reshare a mounted share. At this point nfs is complaining its not a local file path. You would have the same issue if you mounted a NAS directory over and then expected FOG to image to that mounted NAS directory.

      (first I’m ignorant with AWS) It would be better if you created a FOG Storage node in AWS and connect your AWS storage as the boot drive to the is AWS storage, or mount the AWS drive over /images so its a block level device and not a file level device.

      There is an nfs option to crossmount shares. I’ve never used it since its generally a bad idea in most cases. But you can look into that option too.

      Once last idea would be a iscsi mounted volume. That should appear to nfs as a block level file system. Is it possible to create a iSCSI target in AWS?

      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 Aug 8, 2019, 1:50 PM Reply Quote 0
      • Q
        Quazz Moderator
        last edited by Quazz Aug 8, 2019, 6:22 AM Aug 8, 2019, 12:21 PM

        After you update /etc/exports, you have to make sure they’re loaded.

        exportfs -ra

        I’m unfamiliar with AWS EFS, though.

        S 1 Reply Last reply Aug 8, 2019, 1:48 PM Reply Quote 0
        • S
          spidajon @Quazz
          last edited by Aug 8, 2019, 1:48 PM

          @Quazz

          This is what I get after making changes in /etc/exports and running “exportfs -ra”

          exportfs: /efs-aws/dev does not support NFS export
          exportfs: /efs-aws does not support NFS export

          Q 1 Reply Last reply Aug 8, 2019, 1:50 PM Reply Quote 0
          • Q
            Quazz Moderator @spidajon
            last edited by Quazz Aug 8, 2019, 7:50 AM Aug 8, 2019, 1:50 PM

            @spidajon How is the EFS AWS mounted? I think George is right in that you are trying to export a location that is mounted from elsewhere already, which is not possible as far as I know.

            If so, you should follow his advice on how to handle the situation, if that is possible.

            S 1 Reply Last reply Aug 8, 2019, 1:54 PM Reply Quote 0
            • S
              spidajon @george1421
              last edited by Aug 8, 2019, 1:50 PM

              @george1421

              I’ll try some of your suggestions. Not sure you can create a iSCSI target in AWS tho

              1 Reply Last reply Reply Quote 0
              • S
                spidajon @Quazz
                last edited by spidajon Aug 8, 2019, 7:56 AM Aug 8, 2019, 1:54 PM

                @Quazz

                The EFS is mounted already to my VM, its mounted via DNS and the EFS is mounted to the /efs-aws directory. This is how it looks when you type “df -h”. I moved the images over to the directory hence the 9.2G data/images that is in the directory. So its mounted and accessible I just get the “Mounting File system … failed” and the permission denied under the reason in the picture.

                fs-xxxxxx.efs.us-east-1.amazonaws.com😕 8.0E 9.2G 8.0E 1% /efs-aws

                Q 1 Reply Last reply Aug 8, 2019, 1:58 PM Reply Quote 0
                • Q
                  Quazz Moderator @spidajon
                  last edited by Aug 8, 2019, 1:58 PM

                  @spidajon That looks like an NFS mount. You can’t export something that’s mounted onto your system. (you can’t daisy-chain)

                  So in other words, you need to try and do it directly, by for example creating a storage node in the web UI and adding the address there directly.

                  G 1 Reply Last reply Aug 8, 2019, 3:26 PM Reply Quote 0
                  • G
                    george1421 Moderator @Quazz
                    last edited by george1421 Aug 8, 2019, 9:28 AM Aug 8, 2019, 3:26 PM

                    To say it in a MS Windows terms (which also doesn’t support this). Lets say you have server A and you share a directory. On server B you connect Server A’s share to the W: drive. On server B you are try to share the W: drive. The share fails because you are trying to reshare a mounted share. Again this is a file level share. You may be able to do this with a block level share (as an iSCSI volume), but I haven’t tried.

                    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
                    • 1 / 1
                    1 / 1
                    • First post
                      9/9
                      Last post

                    219

                    Online

                    12.1k

                    Users

                    17.3k

                    Topics

                    155.4k

                    Posts
                    Copyright © 2012-2024 FOG Project