<?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: fs_async in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/fs-async/m-p/2806011#M83033</link>
    <description>Ted - I assume you're referring to moving the async driver into the kernel and then performing the mknod.  Yes, we did that a couple of years back on our K-class servers and again on our N4000 servers when we implemented them in 2000.&lt;BR /&gt;&lt;BR /&gt;The dba's use the async drivers for their raw devices.  However, they've chosen to put their tempdb on a filesystem structure instead of raws and I'm wondering about fs_async on filesystems to gain performance of the tempdb for them.&lt;BR /&gt;&lt;BR /&gt;I've heard that fs_asyn is only for HFS which to me is taking a step backwards.&lt;BR /&gt;&lt;BR /&gt;On our DataWarehouse server, we run Oracle on filesystems and have On-line JFS utilizing the mincache and convosync options.  Difference here is that we havn't purchased On-line JFS for the server in question.</description>
    <pubDate>Fri, 13 Sep 2002 15:20:33 GMT</pubDate>
    <dc:creator>Darren Gibbs</dc:creator>
    <dc:date>2002-09-13T15:20:33Z</dc:date>
    <item>
      <title>fs_async</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fs-async/m-p/2806007#M83029</link>
      <description>Our Sybase team wishes to turn on fs_async for filesystems because their tempdb is on a mounted filesystem instead of raws.  My concern with making this change is what effect it will have on all other filesystems on the server?&lt;BR /&gt;&lt;BR /&gt;Can I limit the fs_async usage to specific filesystems via mount options?  BTW - All of our filesystems, except /stand, are vxfs.  We do not have On_Line JFS on this server.</description>
      <pubDate>Fri, 13 Sep 2002 13:52:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fs-async/m-p/2806007#M83029</guid>
      <dc:creator>Darren Gibbs</dc:creator>
      <dc:date>2002-09-13T13:52:35Z</dc:date>
    </item>
    <item>
      <title>Re: fs_async</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fs-async/m-p/2806008#M83030</link>
      <description>fs_async is only for HFS... so don't worry about that for VxFS.</description>
      <pubDate>Fri, 13 Sep 2002 13:59:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fs-async/m-p/2806008#M83030</guid>
      <dc:creator>Dietmar Konermann</dc:creator>
      <dc:date>2002-09-13T13:59:40Z</dc:date>
    </item>
    <item>
      <title>Re: fs_async</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fs-async/m-p/2806009#M83031</link>
      <description>you sure they are not referring to creating the async device that can be used for asycronous transfer... we have that set for Sybase here... to create it:&lt;BR /&gt;&lt;BR /&gt;cd /dev&lt;BR /&gt;mknod async c 101 0x000004 &lt;BR /&gt;&lt;BR /&gt;then change it to have sybase ownership and the DBA team can use that device for async work with the database... check with them and see if that is what they are after, as this will impact the database operation.</description>
      <pubDate>Fri, 13 Sep 2002 14:47:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fs-async/m-p/2806009#M83031</guid>
      <dc:creator>Ted Ellis_2</dc:creator>
      <dc:date>2002-09-13T14:47:28Z</dc:date>
    </item>
    <item>
      <title>Re: fs_async</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fs-async/m-p/2806010#M83032</link>
      <description>Hi&lt;BR /&gt;Check this thread out.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x8995663ce855d511abcd0090277a778c,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x8995663ce855d511abcd0090277a778c,00.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;Prashant.</description>
      <pubDate>Fri, 13 Sep 2002 14:51:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fs-async/m-p/2806010#M83032</guid>
      <dc:creator>Deshpande Prashant</dc:creator>
      <dc:date>2002-09-13T14:51:23Z</dc:date>
    </item>
    <item>
      <title>Re: fs_async</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fs-async/m-p/2806011#M83033</link>
      <description>Ted - I assume you're referring to moving the async driver into the kernel and then performing the mknod.  Yes, we did that a couple of years back on our K-class servers and again on our N4000 servers when we implemented them in 2000.&lt;BR /&gt;&lt;BR /&gt;The dba's use the async drivers for their raw devices.  However, they've chosen to put their tempdb on a filesystem structure instead of raws and I'm wondering about fs_async on filesystems to gain performance of the tempdb for them.&lt;BR /&gt;&lt;BR /&gt;I've heard that fs_asyn is only for HFS which to me is taking a step backwards.&lt;BR /&gt;&lt;BR /&gt;On our DataWarehouse server, we run Oracle on filesystems and have On-line JFS utilizing the mincache and convosync options.  Difference here is that we havn't purchased On-line JFS for the server in question.</description>
      <pubDate>Fri, 13 Sep 2002 15:20:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fs-async/m-p/2806011#M83033</guid>
      <dc:creator>Darren Gibbs</dc:creator>
      <dc:date>2002-09-13T15:20:33Z</dc:date>
    </item>
  </channel>
</rss>

