Debian amd64 mirror size too largeWhich version of debian distro shall I install to my server?linux LVM...

Using std::set container for range items

Where was Karl Mordo in Infinity War?

What type of postprocessing gives the effect of people standing out

I can't die. Who am I?

What should one use the left pedal for on an upright?

Is there a German word for “analytics”?

In the comics did Thanos "kill" just sentient beings or all creatures with the snap?

A "strange" unit radio astronomy

Skis versus snow shoes - when to choose which for travelling the backcountry?

Can we carry rice to Japan?

What's the difference between a cart and a wagon?

Real life puzzle: Unknown alphabet or shorthand

Tcolorbox as an item in list environment

Is the set of paths between any two points moving only in units on the plane countable or uncountable?

Infrastructure damage from sudden thickening of water

Called into a meeting and told we are being made redundant (laid off) and "not to share outside". Can I tell my partner?

Logistics of a hovering watercraft in a fantasy setting

Pure Functions: Does "No Side Effects" Imply "Always Same Output, Given Same Input"?

How to count occurrences of Friday 13th

Is it possible to convert a suspension fork to rigid by drilling it?

How to mitigate "bandwagon attacking" from players?

When was drinking water recognized as crucial in marathon running?

Does Garmin Oregon 700 have Strava integration?

Inverse of the covariance matrix of a multivariate normal distribution



Debian amd64 mirror size too large


Which version of debian distro shall I install to my server?linux LVM mirror vs. MD mirrorCompile a debian package for amd64 on a i386 machine?Clone/Mirror Live Linux (Debian) ServerDebian mirror syncing errormirror server for clusteringSlow download speeds (own debian mirror)debian mirror : Hash Sum mismatchSQL Server Mirror issue on Mirror sideAdditional Debian packages installed by firmware-9.5.0-amd64-netinst.iso













0















I have rsync'ed debian amd64 to my local (Omnios) box using the recommended ftpsync too.



The size of my mirror is 143 GB. I was led to believe from debian and other sources it should be around 80 GB.



here my ftpsync.conf:



MIRRORNAME=`hostname`
TO="/opt/local/share/httpd/htdocs/debian"
RSYNC_PATH="debian/"
RSYNC_HOST=mirrors.dotsrc.org
LOGDIR="${BASEDIR}/log"
LOG="${LOGDIR}/${NAME}.log"
ARCH_EXCLUDE="alpha arm armel armhf hppa hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 m68k mipsel mips powerpc s390 s390x sh sparc source"
LOGROTATE=14
LOCK="${TO}/Archive-Update-in-Progress-${MIRRORNAME}"


rsync-ftpsync.error.0 has no errors.



Why is my mirror so large?










share|improve this question














bumped to the homepage by Community 4 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    0















    I have rsync'ed debian amd64 to my local (Omnios) box using the recommended ftpsync too.



    The size of my mirror is 143 GB. I was led to believe from debian and other sources it should be around 80 GB.



    here my ftpsync.conf:



    MIRRORNAME=`hostname`
    TO="/opt/local/share/httpd/htdocs/debian"
    RSYNC_PATH="debian/"
    RSYNC_HOST=mirrors.dotsrc.org
    LOGDIR="${BASEDIR}/log"
    LOG="${LOGDIR}/${NAME}.log"
    ARCH_EXCLUDE="alpha arm armel armhf hppa hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 m68k mipsel mips powerpc s390 s390x sh sparc source"
    LOGROTATE=14
    LOCK="${TO}/Archive-Update-in-Progress-${MIRRORNAME}"


    rsync-ftpsync.error.0 has no errors.



    Why is my mirror so large?










    share|improve this question














    bumped to the homepage by Community 4 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0








      I have rsync'ed debian amd64 to my local (Omnios) box using the recommended ftpsync too.



      The size of my mirror is 143 GB. I was led to believe from debian and other sources it should be around 80 GB.



      here my ftpsync.conf:



      MIRRORNAME=`hostname`
      TO="/opt/local/share/httpd/htdocs/debian"
      RSYNC_PATH="debian/"
      RSYNC_HOST=mirrors.dotsrc.org
      LOGDIR="${BASEDIR}/log"
      LOG="${LOGDIR}/${NAME}.log"
      ARCH_EXCLUDE="alpha arm armel armhf hppa hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 m68k mipsel mips powerpc s390 s390x sh sparc source"
      LOGROTATE=14
      LOCK="${TO}/Archive-Update-in-Progress-${MIRRORNAME}"


      rsync-ftpsync.error.0 has no errors.



      Why is my mirror so large?










      share|improve this question














      I have rsync'ed debian amd64 to my local (Omnios) box using the recommended ftpsync too.



      The size of my mirror is 143 GB. I was led to believe from debian and other sources it should be around 80 GB.



      here my ftpsync.conf:



      MIRRORNAME=`hostname`
      TO="/opt/local/share/httpd/htdocs/debian"
      RSYNC_PATH="debian/"
      RSYNC_HOST=mirrors.dotsrc.org
      LOGDIR="${BASEDIR}/log"
      LOG="${LOGDIR}/${NAME}.log"
      ARCH_EXCLUDE="alpha arm armel armhf hppa hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 m68k mipsel mips powerpc s390 s390x sh sparc source"
      LOGROTATE=14
      LOCK="${TO}/Archive-Update-in-Progress-${MIRRORNAME}"


      rsync-ftpsync.error.0 has no errors.



      Why is my mirror so large?







      debian mirror






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 16 '14 at 15:58









      JepperJepper

      222312




      222312





      bumped to the homepage by Community 4 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 4 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          My assumption would be because it mirrors both 'amd64' and 'all', both of which are >90GB ( https://www.debian.org/mirror/size ). My ARCH_EXCLUDE is the same as what you've posted, and my mirror is ~162GB currently.



          If you don't need a full mirror you'll probably save a LOT of space if you use a proxy server - https://packages.debian.org/wheezy/apt-cacher-ng



          If you're just spinning up a lot of similar virtual machines or something, your proxy cache may be less than 10GB (just guessing).






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "2"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f576006%2fdebian-amd64-mirror-size-too-large%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            My assumption would be because it mirrors both 'amd64' and 'all', both of which are >90GB ( https://www.debian.org/mirror/size ). My ARCH_EXCLUDE is the same as what you've posted, and my mirror is ~162GB currently.



            If you don't need a full mirror you'll probably save a LOT of space if you use a proxy server - https://packages.debian.org/wheezy/apt-cacher-ng



            If you're just spinning up a lot of similar virtual machines or something, your proxy cache may be less than 10GB (just guessing).






            share|improve this answer




























              0














              My assumption would be because it mirrors both 'amd64' and 'all', both of which are >90GB ( https://www.debian.org/mirror/size ). My ARCH_EXCLUDE is the same as what you've posted, and my mirror is ~162GB currently.



              If you don't need a full mirror you'll probably save a LOT of space if you use a proxy server - https://packages.debian.org/wheezy/apt-cacher-ng



              If you're just spinning up a lot of similar virtual machines or something, your proxy cache may be less than 10GB (just guessing).






              share|improve this answer


























                0












                0








                0







                My assumption would be because it mirrors both 'amd64' and 'all', both of which are >90GB ( https://www.debian.org/mirror/size ). My ARCH_EXCLUDE is the same as what you've posted, and my mirror is ~162GB currently.



                If you don't need a full mirror you'll probably save a LOT of space if you use a proxy server - https://packages.debian.org/wheezy/apt-cacher-ng



                If you're just spinning up a lot of similar virtual machines or something, your proxy cache may be less than 10GB (just guessing).






                share|improve this answer













                My assumption would be because it mirrors both 'amd64' and 'all', both of which are >90GB ( https://www.debian.org/mirror/size ). My ARCH_EXCLUDE is the same as what you've posted, and my mirror is ~162GB currently.



                If you don't need a full mirror you'll probably save a LOT of space if you use a proxy server - https://packages.debian.org/wheezy/apt-cacher-ng



                If you're just spinning up a lot of similar virtual machines or something, your proxy cache may be less than 10GB (just guessing).







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jul 24 '14 at 14:18









                anonanon

                1




                1






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Server Fault!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f576006%2fdebian-amd64-mirror-size-too-large%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Фонтен-ла-Гаярд Зміст Демографія | Економіка | Посилання |...

                    Список ссавців Італії Природоохоронні статуси | Список |...

                    Маріан Котлеба Зміст Життєпис | Політичні погляди |...