<?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: block size per write in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/block-size-per-write/m-p/2826224#M87671</link>
    <description>The size of writes is governed by the application and specifically by the nbytes parameter to the read() system call. This parameter can vary from write() to write(). One of the best ways is to install tusc.&lt;BR /&gt;&lt;A href="http://gatekeep.cs.utah.edu/hppd/hpux/Sysadmin/tusc-7.3/" target="_blank"&gt;http://gatekeep.cs.utah.edu/hppd/hpux/Sysadmin/tusc-7.3/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Tusc will allow you to trace system calls and actually see the values passed to the system calls. That will enable you to get an exact answer.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 15 Oct 2002 18:14:21 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2002-10-15T18:14:21Z</dc:date>
    <item>
      <title>block size per write</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/block-size-per-write/m-p/2826222#M87669</link>
      <description>How can I determine what my block size is per write to disk on the O/S</description>
      <pubDate>Tue, 15 Oct 2002 15:35:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/block-size-per-write/m-p/2826222#M87669</guid>
      <dc:creator>Eric Hess</dc:creator>
      <dc:date>2002-10-15T15:35:54Z</dc:date>
    </item>
    <item>
      <title>Re: block size per write</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/block-size-per-write/m-p/2826223#M87670</link>
      <description>&lt;BR /&gt;What are you using to write??&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Tue, 15 Oct 2002 16:03:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/block-size-per-write/m-p/2826223#M87670</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2002-10-15T16:03:08Z</dc:date>
    </item>
    <item>
      <title>Re: block size per write</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/block-size-per-write/m-p/2826224#M87671</link>
      <description>The size of writes is governed by the application and specifically by the nbytes parameter to the read() system call. This parameter can vary from write() to write(). One of the best ways is to install tusc.&lt;BR /&gt;&lt;A href="http://gatekeep.cs.utah.edu/hppd/hpux/Sysadmin/tusc-7.3/" target="_blank"&gt;http://gatekeep.cs.utah.edu/hppd/hpux/Sysadmin/tusc-7.3/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Tusc will allow you to trace system calls and actually see the values passed to the system calls. That will enable you to get an exact answer.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 15 Oct 2002 18:14:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/block-size-per-write/m-p/2826224#M87671</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2002-10-15T18:14:21Z</dc:date>
    </item>
    <item>
      <title>Re: block size per write</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/block-size-per-write/m-p/2826225#M87672</link>
      <description>Hi Eric,&lt;BR /&gt;&lt;BR /&gt;It really depends on your application. There are two kinds of block sizes - File system block size and the physical disk block size (512 bytes or a sector). Physical disk block size is masked by the File system block size.&lt;BR /&gt;I believe you meant IO size. &lt;BR /&gt;&lt;BR /&gt;The IO size is dependent on random, sequential, synchronous and asynchronous, discovered direct etc., Applications like Oracle can give a good picture of it's IO.&lt;BR /&gt;&lt;BR /&gt;One of the major advantages of having VxVM against LVM is that it provides a utility called "vxtrace" that can be used to determine the type and size of IO. Unless you have VxVM or you know how your application writes, it is not possible to determine the IO details.&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
      <pubDate>Tue, 15 Oct 2002 18:32:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/block-size-per-write/m-p/2826225#M87672</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2002-10-15T18:32:26Z</dc:date>
    </item>
    <item>
      <title>Re: block size per write</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/block-size-per-write/m-p/2826226#M87673</link>
      <description>Hi Eric &lt;BR /&gt;&lt;BR /&gt;U can get the filesystem block size by typing the command &lt;BR /&gt;fstyp -v /dev/vg##/lvol# . &lt;BR /&gt;By this command u will come to know what is the filesystem block size . &lt;BR /&gt;Actually in HP-UX allocation is on a random basis depending on the size of data being written on to the disk. &lt;BR /&gt;&lt;BR /&gt;Sanjeev &lt;BR /&gt;</description>
      <pubDate>Wed, 16 Oct 2002 04:43:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/block-size-per-write/m-p/2826226#M87673</guid>
      <dc:creator>Sanjeev Kohli_1</dc:creator>
      <dc:date>2002-10-16T04:43:17Z</dc:date>
    </item>
  </channel>
</rss>

