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

    image/. file is at 265+ G and crashing several nodes- keeps growing

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    5
    775
    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.
    • LPetelikL
      LPetelik
      last edited by LPetelik

      Server
      • FOG Version: 1.33, most nodes at 1.3.3 also

      • OS:

      Client
      • Service Version:
      • OS:
      Description

      I have a set up with a master and 16 nodes. I came in this morning to 8 nodes down due to space. I’ve found that at /images there is “.” at 268 G on one of the servers (probably all of them). I can’t get servers back up because as soon as I make space, it’s getting used again. I think I know the offending image and I’ve removed it from the group that it’s replicating to. I’m on the node that’s causing the issue but I’m not sure how to clean up the “.” file.

      Any advice would be very welcome.

      0_1504195333630_d8ad0dc0-6b04-419c-ad83-c5c493b0020f-image.png

      Wayne WorkmanW 1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by Sebastian Roth

        @LPetelik Trying to contact you on forum chat…

        By the way, “.” is just the current directory, meaning the sum of all subdirectories within your /images folder is growing or possibly is just a file directly in /images?!?

        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

        1 Reply Last reply Reply Quote 2
        • Wayne WorkmanW
          Wayne Workman @LPetelik
          last edited by

          @lpetelik Look at the output of this on that node: ls -laht /images it should tell you where the space is going. You can also try du -sh /images/* and you might also look at the output of df -h for 100% full partitions.

          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 1
          • S
            Sebastian Roth Moderator
            last edited by

            @Wayne-Workman We are working on this in chat. Cleaned it mostly up already.

            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

            1 Reply Last reply Reply Quote 1
            • LPetelikL
              LPetelik
              last edited by

              This is solved from a FOG point of view.

              The problem was that a user replicated several large images overnight and Hyper-V expanded the VM, choking the main servers.

              Thank you for all of your help @Sebastian-Roth!

              1 Reply Last reply Reply Quote 2
              • 1 / 1
              • First post
                Last post

              169

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project