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

    No shrink from V1.5.5 until V1.6, deploy error, 100%CPU load in node 1.5.2

    Scheduled Pinned Locked Moved Solved
    Bug Reports
    3
    11
    934
    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.
    • Q
      Quazz Moderator
      last edited by

      Try the latest init files. You need to manually download those from our server. https://fogproject.org/inits/init_32.xz and https://fogproject.org/inits/init.xz

      H 1 Reply Last reply Reply Quote 1
      • H
        HG12
        last edited by

        This post is deleted!
        1 Reply Last reply Reply Quote 0
        • H
          HG12 @Quazz
          last edited by

          @Quazz said in No shrink from V1.5.5 until V1.6, deploy error, 100%CPU load in node 1.5.2:

          Try the latest init files. You need to manually download those from our server. https://fogproject.org/inits/init_32.xz and https://fogproject.org/inits/init.xz

          I have downlaod the files, but are the same file in my V1.5.5.
          I downloaded the fogproject-dev-branch1.5.5.3 for tests but in V1.5.5.3 is the same error with Zstd.
          Now I have the used init files from the V1.5.2 put it into V1.5.5.3.
          Now the SSD will be shrink with Partclone/ Zstd in V1.5.5.3.
          Is the init file not compatible with my optiplex 9010?
          At this weekend I will test image.

          Q 1 Reply Last reply Reply Quote 0
          • Q
            Quazz Moderator @HG12
            last edited by Quazz

            @HG12 There were some changes to how to detect which partitions to resize and which not.

            It’s supposed to not mark a single partition disk as fixed size, but it appears that’s not really working as expected, but looking over the code I’m unsure as to why.

            edit: Ah, think I may have found the problem.

            @Sebastian-Roth

            https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L462

            Why don’t we just test for if [[ $is_fixed -eq 1 ]] like on line https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L439

            This would simplify the code and put the logic on the initial fixed size file creation which makes more sense, imo.

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

              @Quazz Not exactly sure how you mean to use is_fixed in case of single partition disk?! May I ask you to send a pull request on that so we can elaborate on the code more directly?

              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

              Q 2 Replies Last reply Reply Quote 0
              • Q
                Quazz Moderator @Sebastian Roth
                last edited by

                @Sebastian-Roth No, I mean in general, since the logic to extract fixed partitions and handle single partitions is already done in bin/fog.upload which is where the is_fixed variable is based on anyway.

                1 Reply Last reply Reply Quote 0
                • H
                  HG12 @Quazz
                  last edited by

                  @Quazz
                  Thanks for helping, I will test it next week. Today is end of working day.
                  I send feedback.

                  Q 1 Reply Last reply Reply Quote 0
                  • Q
                    Quazz Moderator @Sebastian Roth
                    last edited by Quazz

                    @Sebastian-Roth https://github.com/FOGProject/fos/pull/24

                    @HG12 Hopefully new inits will be available then!

                    1 Reply Last reply Reply Quote 1
                    • Q
                      Quazz Moderator @HG12
                      last edited by

                      @HG12 Hey, it’s been a while, is this issue resolved? There are updated inits available (I think) that might have resolved this issue.

                      H 1 Reply Last reply Reply Quote 0
                      • H
                        HG12 @Quazz
                        last edited by

                        @Quazz I´m sorry, I was sick for a long time. Now this day is my first day. I will test it if I have time. But I´m busy with an other project. I hope I can test it next week. Please don´t close this thread. Thanks

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

                        205

                        Online

                        12.1k

                        Users

                        17.3k

                        Topics

                        155.4k

                        Posts
                        Copyright © 2012-2024 FOG Project