<?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 Blocking factor on tar in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/blocking-factor-on-tar/m-p/3343007#M191053</link>
    <description>I have obviously misunderstood the use of the blocking factor on tar.  I am having problems with slow DLT drives and one sugegstion is to up the blocking factor to 64.  Now to me that makes sense 64*512 bytes is 32k and thats the size block I am trying to get to.  However when I run tar -b64 -cvf /dev/rmt/0m .....&lt;BR /&gt;&lt;BR /&gt;I get Invalid blocksize. (Max 64)&lt;BR /&gt;&lt;BR /&gt;Isnt my blocksize 32 when using a blocking cator of 64?????</description>
    <pubDate>Wed, 28 Jul 2004 03:42:48 GMT</pubDate>
    <dc:creator>Scott Dunkley</dc:creator>
    <dc:date>2004-07-28T03:42:48Z</dc:date>
    <item>
      <title>Blocking factor on tar</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/blocking-factor-on-tar/m-p/3343007#M191053</link>
      <description>I have obviously misunderstood the use of the blocking factor on tar.  I am having problems with slow DLT drives and one sugegstion is to up the blocking factor to 64.  Now to me that makes sense 64*512 bytes is 32k and thats the size block I am trying to get to.  However when I run tar -b64 -cvf /dev/rmt/0m .....&lt;BR /&gt;&lt;BR /&gt;I get Invalid blocksize. (Max 64)&lt;BR /&gt;&lt;BR /&gt;Isnt my blocksize 32 when using a blocking cator of 64?????</description>
      <pubDate>Wed, 28 Jul 2004 03:42:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/blocking-factor-on-tar/m-p/3343007#M191053</guid>
      <dc:creator>Scott Dunkley</dc:creator>
      <dc:date>2004-07-28T03:42:48Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking factor on tar</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/blocking-factor-on-tar/m-p/3343008#M191054</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Try&lt;BR /&gt;&lt;BR /&gt;tar -cvf /dev/rmt/0m -b 64&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;           Steve Steel</description>
      <pubDate>Wed, 28 Jul 2004 03:57:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/blocking-factor-on-tar/m-p/3343008#M191054</guid>
      <dc:creator>Steve Steel</dc:creator>
      <dc:date>2004-07-28T03:57:44Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking factor on tar</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/blocking-factor-on-tar/m-p/3343009#M191055</link>
      <description>Ok so I tried it that way: &lt;BR /&gt;&lt;BR /&gt;$ tar -cvf /dev/rmt/0mn -b 64 /etc/hosts&lt;BR /&gt;tar: cannot stat -b.  Not dumped.&lt;BR /&gt;tar: cannot stat 64.  Not dumped.&lt;BR /&gt;a /etc/hosts 2 blocks&lt;BR /&gt;&lt;BR /&gt;It tries to backup a file called -b a 64 so I put the -b 64 or -b64 at the end like:&lt;BR /&gt;&lt;BR /&gt;$ tar -cvf /dev/rmt/0mn /etc/hosts -b64&lt;BR /&gt;a /etc/hosts 2 blocks&lt;BR /&gt;tar: cannot stat -b64.  Not dumped&lt;BR /&gt;&lt;BR /&gt;and it still tries to backup a file called -b64 or -b and 64.&lt;BR /&gt;&lt;BR /&gt;any other suggestions.</description>
      <pubDate>Wed, 28 Jul 2004 04:01:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/blocking-factor-on-tar/m-p/3343009#M191055</guid>
      <dc:creator>Scott Dunkley</dc:creator>
      <dc:date>2004-07-28T04:01:21Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking factor on tar</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/blocking-factor-on-tar/m-p/3343010#M191056</link>
      <description>hi&lt;BR /&gt;&lt;BR /&gt;Block size cannot be more than 20. Check out the man page for blocking factor. &lt;BR /&gt;&lt;BR /&gt;rgrds&lt;BR /&gt;[V]</description>
      <pubDate>Wed, 28 Jul 2004 05:16:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/blocking-factor-on-tar/m-p/3343010#M191056</guid>
      <dc:creator>S. Singaravelu</dc:creator>
      <dc:date>2004-07-28T05:16:33Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking factor on tar</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/blocking-factor-on-tar/m-p/3343011#M191057</link>
      <description>yes it can it can be upto 64 and this is what I have been advised to try by HP to get round the slow speed of tar on DLT8000 using latest firmware.  64 is the maximum.&lt;BR /&gt;&lt;BR /&gt;I have got it to work but not with the -f option as well.  If I do:&lt;BR /&gt;&lt;BR /&gt;tar -cvb 64 /etc/hosts&lt;BR /&gt;&lt;BR /&gt;it works ok and backups to the default /dev/rmt/0m location but when you try and add in a non default destination using -f this is when I hit the issues highlighted.</description>
      <pubDate>Wed, 28 Jul 2004 05:22:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/blocking-factor-on-tar/m-p/3343011#M191057</guid>
      <dc:creator>Scott Dunkley</dc:creator>
      <dc:date>2004-07-28T05:22:06Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking factor on tar</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/blocking-factor-on-tar/m-p/3343012#M191058</link>
      <description>Ok I have worked it out after reading the man page 3 or 4 times I now understand.&lt;BR /&gt;&lt;BR /&gt;tar -cvfb /dev/rmt/0m 64 /etc/hosts&lt;BR /&gt;&lt;BR /&gt;the order of the arguemnet list matters.  Becuase the f is before the b the device file has to be before the blocking factor number.</description>
      <pubDate>Wed, 28 Jul 2004 05:33:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/blocking-factor-on-tar/m-p/3343012#M191058</guid>
      <dc:creator>Scott Dunkley</dc:creator>
      <dc:date>2004-07-28T05:33:07Z</dc:date>
    </item>
  </channel>
</rss>

