Why does tar appear to skip file contents when output file is /dev/null? The 2019 Stack...

Why use ultrasound for medical imaging?

Format single node in tikzcd

Wall plug outlet change

Can the prologue be the backstory of your main character?

What LEGO pieces have "real-world" functionality?

What's the point in a preamp?

How to delete random line from file using Unix command?

Why does tar appear to skip file contents when output file is /dev/null?

ELI5: Why do they say that Israel would have been the fourth country to land a spacecraft on the Moon and why do they call it low cost?

In horse breeding, what is the female equivalent of putting a horse out "to stud"?

What are these Gizmos at Izaña Atmospheric Research Center in Spain?

Do warforged have souls?

What does the torsion-free condition for a connection mean in terms of its horizontal bundle?

How can I define good in a religion that claims no moral authority?

How to make `trap` know if the EXIT is after successful program finish or because of premature as an error or something

Do working physicists consider Newtonian mechanics to be "falsified"?

The variadic template constructor of my class cannot modify my class members, why is that so?

"... to apply for a visa" or "... and applied for a visa"?

Would an alien lifeform be able to achieve space travel if lacking in vision?

Match Roman Numerals

Did the new image of black hole confirm the general theory of relativity?

Single author papers against my advisor's will?

How can I protect witches in combat who wear limited clothing?

How should I replace vector<uint8_t>::const_iterator in an API?



Why does tar appear to skip file contents when output file is /dev/null?



The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election ResultsWhy is my tar file bigger than its contents?mv a file to /dev/null breaks dev/nulltar: /dev/st0: Cannot write: Input/output errorMeaning of `cat /dev/null > file`Output file generated by tarWhy does my tar not work?What happens when you write to /dev/null? What’s the point?Why is /dev/null a file? Why isn't its function implemented as a simple program?Make tar from /dev/stdin fileCompare file compression methods by sending to /dev/null





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







2















I have a directory with over 400 GiB of data in it. I wanted to check that all the files can be read without errors, so a simple way I thought of was to tar it into /dev/null. But instead I see the following behavior:



$ time tar cf /dev/null .

real 0m4.387s
user 0m3.462s
sys 0m0.185s
$ time tar cf - . > /dev/null

real 0m3.130s
user 0m3.091s
sys 0m0.035s
$ time tar cf - . | cat > /dev/null
^C

real 10m32.985s
user 0m1.942s
sys 0m33.764s


The third command above was forcibly stopped by Ctrl+C after having run for quite long already. Moreover, while the first two commands were working, activity indicator of the storage device containing . was nearly always idle. With the third command the indicator is constantly lit up, meaning extreme busyness.



So it seems that, when tar is able to find out that its output file is /dev/null, i.e. when /dev/null is directly opened to have the file handle which tar writes to, file body appears skipped. (Adding v option to tar does print all the files in the directory being tar'red.)



So I wonder, why is this so? Is it some kind of optimization? If yes, then why would tar even want to do such a dubious optimization for such a special case?



I'm using GNU tar 1.26 with glibc 2.27 on Linux 4.14.105 amd64.










share|improve this question





























    2















    I have a directory with over 400 GiB of data in it. I wanted to check that all the files can be read without errors, so a simple way I thought of was to tar it into /dev/null. But instead I see the following behavior:



    $ time tar cf /dev/null .

    real 0m4.387s
    user 0m3.462s
    sys 0m0.185s
    $ time tar cf - . > /dev/null

    real 0m3.130s
    user 0m3.091s
    sys 0m0.035s
    $ time tar cf - . | cat > /dev/null
    ^C

    real 10m32.985s
    user 0m1.942s
    sys 0m33.764s


    The third command above was forcibly stopped by Ctrl+C after having run for quite long already. Moreover, while the first two commands were working, activity indicator of the storage device containing . was nearly always idle. With the third command the indicator is constantly lit up, meaning extreme busyness.



    So it seems that, when tar is able to find out that its output file is /dev/null, i.e. when /dev/null is directly opened to have the file handle which tar writes to, file body appears skipped. (Adding v option to tar does print all the files in the directory being tar'red.)



    So I wonder, why is this so? Is it some kind of optimization? If yes, then why would tar even want to do such a dubious optimization for such a special case?



    I'm using GNU tar 1.26 with glibc 2.27 on Linux 4.14.105 amd64.










    share|improve this question

























      2












      2








      2


      1






      I have a directory with over 400 GiB of data in it. I wanted to check that all the files can be read without errors, so a simple way I thought of was to tar it into /dev/null. But instead I see the following behavior:



      $ time tar cf /dev/null .

      real 0m4.387s
      user 0m3.462s
      sys 0m0.185s
      $ time tar cf - . > /dev/null

      real 0m3.130s
      user 0m3.091s
      sys 0m0.035s
      $ time tar cf - . | cat > /dev/null
      ^C

      real 10m32.985s
      user 0m1.942s
      sys 0m33.764s


      The third command above was forcibly stopped by Ctrl+C after having run for quite long already. Moreover, while the first two commands were working, activity indicator of the storage device containing . was nearly always idle. With the third command the indicator is constantly lit up, meaning extreme busyness.



      So it seems that, when tar is able to find out that its output file is /dev/null, i.e. when /dev/null is directly opened to have the file handle which tar writes to, file body appears skipped. (Adding v option to tar does print all the files in the directory being tar'red.)



      So I wonder, why is this so? Is it some kind of optimization? If yes, then why would tar even want to do such a dubious optimization for such a special case?



      I'm using GNU tar 1.26 with glibc 2.27 on Linux 4.14.105 amd64.










      share|improve this question














      I have a directory with over 400 GiB of data in it. I wanted to check that all the files can be read without errors, so a simple way I thought of was to tar it into /dev/null. But instead I see the following behavior:



      $ time tar cf /dev/null .

      real 0m4.387s
      user 0m3.462s
      sys 0m0.185s
      $ time tar cf - . > /dev/null

      real 0m3.130s
      user 0m3.091s
      sys 0m0.035s
      $ time tar cf - . | cat > /dev/null
      ^C

      real 10m32.985s
      user 0m1.942s
      sys 0m33.764s


      The third command above was forcibly stopped by Ctrl+C after having run for quite long already. Moreover, while the first two commands were working, activity indicator of the storage device containing . was nearly always idle. With the third command the indicator is constantly lit up, meaning extreme busyness.



      So it seems that, when tar is able to find out that its output file is /dev/null, i.e. when /dev/null is directly opened to have the file handle which tar writes to, file body appears skipped. (Adding v option to tar does print all the files in the directory being tar'red.)



      So I wonder, why is this so? Is it some kind of optimization? If yes, then why would tar even want to do such a dubious optimization for such a special case?



      I'm using GNU tar 1.26 with glibc 2.27 on Linux 4.14.105 amd64.







      tar null






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 32 mins ago









      RuslanRuslan

      1,3961427




      1,3961427






















          1 Answer
          1






          active

          oldest

          votes


















          4














          It is a documented optimization:




          When the archive is being created to /dev/null, GNU tar tries to
          minimize input and output operations. The Amanda backup system, when
          used with GNU tar, has an initial sizing pass which uses this feature.







          share|improve this answer
























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            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: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            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%2funix.stackexchange.com%2fquestions%2f512362%2fwhy-does-tar-appear-to-skip-file-contents-when-output-file-is-dev-null%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









            4














            It is a documented optimization:




            When the archive is being created to /dev/null, GNU tar tries to
            minimize input and output operations. The Amanda backup system, when
            used with GNU tar, has an initial sizing pass which uses this feature.







            share|improve this answer




























              4














              It is a documented optimization:




              When the archive is being created to /dev/null, GNU tar tries to
              minimize input and output operations. The Amanda backup system, when
              used with GNU tar, has an initial sizing pass which uses this feature.







              share|improve this answer


























                4












                4








                4







                It is a documented optimization:




                When the archive is being created to /dev/null, GNU tar tries to
                minimize input and output operations. The Amanda backup system, when
                used with GNU tar, has an initial sizing pass which uses this feature.







                share|improve this answer













                It is a documented optimization:




                When the archive is being created to /dev/null, GNU tar tries to
                minimize input and output operations. The Amanda backup system, when
                used with GNU tar, has an initial sizing pass which uses this feature.








                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 14 mins ago









                murumuru

                37.7k589165




                37.7k589165






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • 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%2funix.stackexchange.com%2fquestions%2f512362%2fwhy-does-tar-appear-to-skip-file-contents-when-output-file-is-dev-null%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

                    Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

                    Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

                    Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...