<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Tar: blocksize = 0; broken pipe? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/tar-blocksize-0-broken-pipe/m-p/3163582#M569938</link>
    <description>Thanks Elmar, I tried the dd commmand and it did print stuff to the screen but tar still did not work. Did a fbackup and a frecover and we were able to see the data on the tape and work with it. Talking to HP, it is an issue with the tar application itself.&lt;BR /&gt;&lt;BR /&gt;Now it is back to the backup software manufacturer as it is not hardware or O/S.&lt;BR /&gt;&lt;BR /&gt;Thank you for your time. &lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 14 Jan 2004 16:50:04 GMT</pubDate>
    <dc:creator>Kevin Nikiforuk</dc:creator>
    <dc:date>2004-01-14T16:50:04Z</dc:date>
    <item>
      <title>Tar: blocksize = 0; broken pipe?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tar-blocksize-0-broken-pipe/m-p/3163580#M569936</link>
      <description>Hello, &lt;BR /&gt;&lt;BR /&gt;We initially noticed that we were having problems with some of our backups. There would be an I/O error, the tape marked full when only a small amount of data had been written to it (1%+).&lt;BR /&gt;&lt;BR /&gt;We were told to contact the backup software manufacturer who gave us the following procedure (with our results included). I am tar'ing the data to a jubebox with 8 DLT drives. Same result on all drives. &lt;BR /&gt;&lt;BR /&gt;#tar -cvf /dev/rmt/21mnb /home/XXXX/.profile&lt;BR /&gt;a /home/XXXX/.profile 1 blocks&lt;BR /&gt;&lt;BR /&gt;#mt -f /dev/rmt/21mnb rewind     &lt;BR /&gt;&lt;BR /&gt;#tar -xvf /dev/rmt/21mnb&lt;BR /&gt;directory checksum error&lt;BR /&gt;&lt;BR /&gt;I have also checked the this forum link and followed Elmar's instruction but I get the following error :&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=327706" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=327706&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;#tar -tvf /dev/rmt/21mnb&lt;BR /&gt;Tar: blocksize = 0; broken pipe?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;We have also had the hardware manufacturerer in to check the the jubebox and they were able to view all DLT, switches, device messages and there were no error messages.&lt;BR /&gt;&lt;BR /&gt;We have also used many different tapes just to eliminate the bad tape issue. &lt;BR /&gt;&lt;BR /&gt;Is there anything else I can check to see why we are getting the directory checksum error and Tar: blocksize = 0; broken pipe? error?&lt;BR /&gt;&lt;BR /&gt;Thank you in advance.</description>
      <pubDate>Tue, 13 Jan 2004 18:43:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tar-blocksize-0-broken-pipe/m-p/3163580#M569936</guid>
      <dc:creator>Kevin Nikiforuk</dc:creator>
      <dc:date>2004-01-13T18:43:22Z</dc:date>
    </item>
    <item>
      <title>Re: Tar: blocksize = 0; broken pipe?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tar-blocksize-0-broken-pipe/m-p/3163581#M569937</link>
      <description>Have you also checked with specifying the blocksize when tarring to the tapes? Since it is DLT, I would suggest using large blocksizes, at least 32k.&lt;BR /&gt;&lt;BR /&gt;For some reason, tar has trouble reading back the data from the tape.&lt;BR /&gt;&lt;BR /&gt;Since you only backupped (or backed up, a problem for the English speaking people around here) .profile, you could also try to do the rewind and then:&lt;BR /&gt;dd if=/dev/rmt/21mnb bs=512 | cat -tv | pg&lt;BR /&gt;Just to see if any data was really written to tape and if it contains the correct data.&lt;BR /&gt;</description>
      <pubDate>Wed, 14 Jan 2004 02:02:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tar-blocksize-0-broken-pipe/m-p/3163581#M569937</guid>
      <dc:creator>Elmar P. Kolkman</dc:creator>
      <dc:date>2004-01-14T02:02:42Z</dc:date>
    </item>
    <item>
      <title>Re: Tar: blocksize = 0; broken pipe?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tar-blocksize-0-broken-pipe/m-p/3163582#M569938</link>
      <description>Thanks Elmar, I tried the dd commmand and it did print stuff to the screen but tar still did not work. Did a fbackup and a frecover and we were able to see the data on the tape and work with it. Talking to HP, it is an issue with the tar application itself.&lt;BR /&gt;&lt;BR /&gt;Now it is back to the backup software manufacturer as it is not hardware or O/S.&lt;BR /&gt;&lt;BR /&gt;Thank you for your time. &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 14 Jan 2004 16:50:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tar-blocksize-0-broken-pipe/m-p/3163582#M569938</guid>
      <dc:creator>Kevin Nikiforuk</dc:creator>
      <dc:date>2004-01-14T16:50:04Z</dc:date>
    </item>
  </channel>
</rss>

