<?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: Normal for /sbin/bcheckrc to take long time at boot? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604625#M233473</link>
    <description>Hi Mike,&lt;BR /&gt;&lt;BR /&gt;Allthough we do not have VG's on SAN but have VxVM DGs. The DG activation time reduced dramatically when we updraded VxVM to 3.5 from 3.2 last year. We use XP array 1024 &amp;amp; 512.&lt;BR /&gt;&lt;BR /&gt;I would also suggest to look for latest patches and also try to activating VG manually after system is up. This can be done by changing auto activation parameter for non-root vg's in /etc/lvmrc file.&lt;BR /&gt;&lt;BR /&gt;AUTO_VG_ACTIVATE=0 ( For preventing auto activation)&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Devender</description>
    <pubDate>Wed, 17 Aug 2005 00:00:35 GMT</pubDate>
    <dc:creator>Devender Khatana</dc:creator>
    <dc:date>2005-08-17T00:00:35Z</dc:date>
    <item>
      <title>Normal for /sbin/bcheckrc to take long time at boot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604622#M233470</link>
      <description>We recently migrated some of our databases running on a local 12H array to an EMC SAN (CX500). The servers are N4000's. The thing that I notice now is the boot time has slowed dramatically. &lt;BR /&gt;&lt;BR /&gt;During boot, I see the echo for EMC PowerPath starting. The next echo is: /sbin/bcheckrc&lt;BR /&gt;&lt;BR /&gt;I understand this script is going through each filesystem and running fsck and making sure that it is clean and then activating the volume group. vg00 is usually activated within 1 minute. However, the SAN volume groups typically take anywhere from 4 to 6 minutes a piece before they are activated. This his tacked on about 15 - 20 minutes extra to my boot time. &lt;BR /&gt;&lt;BR /&gt;Is there any way to shorten the amount of time that the bcheckrc script takes to run?</description>
      <pubDate>Tue, 16 Aug 2005 08:37:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604622#M233470</guid>
      <dc:creator>Mike Keys</dc:creator>
      <dc:date>2005-08-16T08:37:12Z</dc:date>
    </item>
    <item>
      <title>Re: Normal for /sbin/bcheckrc to take long time at boot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604623#M233471</link>
      <description>This is 'a bit' longer than it usually takes.&lt;BR /&gt;&lt;BR /&gt;There is a certain delay for activating SAN volume groups, as a rough number a larger database host might take 2 minutes for 10 VGs with ~60 LUNs.&lt;BR /&gt;&lt;BR /&gt;I've also seen it take much longer, to the extent of 25 minutes, but in this case we had some definite problems.&lt;BR /&gt;&lt;BR /&gt;some steps You should take:&lt;BR /&gt;- check &lt;BR /&gt;/opt/fcms/bin/tdutil /dev/td&lt;INSTANCE&gt; stat&lt;BR /&gt;output, looking for transmission errors&lt;BR /&gt;- get both CX service processor logs for excessive trespassing (this will only show up as informational, but it may rise to levels above 1000/minute, which will influence the array in a *bad* way)&lt;BR /&gt;You can aquire the SP logs either via the java navisphere thing or using &lt;BR /&gt;/opt/Navisphere/bin/navicli -h &lt;SP ip="" address=""&gt; getlog.&lt;BR /&gt;- check Your kernel setting FCP_MAX_REQUESTS - it defaults to 512 requests per adapter per second, which maybe more than EMC^2 supports - ask them and adjust the value (in our case this definitely solved the issue)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;In short: Either a hardware or a configuration issue.&lt;BR /&gt;If allowable, I'd ask You to post the fcms and sp logs.&lt;BR /&gt;&lt;/SP&gt;&lt;/INSTANCE&gt;</description>
      <pubDate>Tue, 16 Aug 2005 08:55:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604623#M233471</guid>
      <dc:creator>Florian Heigl (new acc)</dc:creator>
      <dc:date>2005-08-16T08:55:13Z</dc:date>
    </item>
    <item>
      <title>Re: Normal for /sbin/bcheckrc to take long time at boot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604624#M233472</link>
      <description>Seems a bit slow. I'd get the SAN side looked at.  &lt;BR /&gt;&lt;BR /&gt;Also, ioscan fnC disk see if there is a problem with alternate paths and such.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 16 Aug 2005 09:13:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604624#M233472</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2005-08-16T09:13:00Z</dc:date>
    </item>
    <item>
      <title>Re: Normal for /sbin/bcheckrc to take long time at boot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604625#M233473</link>
      <description>Hi Mike,&lt;BR /&gt;&lt;BR /&gt;Allthough we do not have VG's on SAN but have VxVM DGs. The DG activation time reduced dramatically when we updraded VxVM to 3.5 from 3.2 last year. We use XP array 1024 &amp;amp; 512.&lt;BR /&gt;&lt;BR /&gt;I would also suggest to look for latest patches and also try to activating VG manually after system is up. This can be done by changing auto activation parameter for non-root vg's in /etc/lvmrc file.&lt;BR /&gt;&lt;BR /&gt;AUTO_VG_ACTIVATE=0 ( For preventing auto activation)&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Devender</description>
      <pubDate>Wed, 17 Aug 2005 00:00:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604625#M233473</guid>
      <dc:creator>Devender Khatana</dc:creator>
      <dc:date>2005-08-17T00:00:35Z</dc:date>
    </item>
    <item>
      <title>Re: Normal for /sbin/bcheckrc to take long time at boot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604626#M233474</link>
      <description>swlist -i shows:&lt;BR /&gt;&lt;BR /&gt;Base-VXVM -&amp;gt; B.03.50.5 on all servers with VG's on SAN.</description>
      <pubDate>Wed, 17 Aug 2005 09:37:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604626#M233474</guid>
      <dc:creator>Mike Keys</dc:creator>
      <dc:date>2005-08-17T09:37:37Z</dc:date>
    </item>
    <item>
      <title>Re: Normal for /sbin/bcheckrc to take long time at boot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604627#M233475</link>
      <description>I would have a look at your bcheckrc file.  It is not uncommon for this to be amended on-site to force a FULL fsck on each filesystem, regardless of the clean flag on the filesystem.  This can cause your system to take longer to boot.</description>
      <pubDate>Wed, 17 Aug 2005 09:43:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604627#M233475</guid>
      <dc:creator>Simon Hargrave</dc:creator>
      <dc:date>2005-08-17T09:43:55Z</dc:date>
    </item>
    <item>
      <title>Re: Normal for /sbin/bcheckrc to take long time at boot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604628#M233476</link>
      <description>Even though the script says not to modify, what should I be looking at in the script?</description>
      <pubDate>Wed, 17 Aug 2005 09:52:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604628#M233476</guid>
      <dc:creator>Mike Keys</dc:creator>
      <dc:date>2005-08-17T09:52:07Z</dc:date>
    </item>
    <item>
      <title>Re: Normal for /sbin/bcheckrc to take long time at boot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604629#M233477</link>
      <description>One more possible reason that just came to my mind would be seeing too many (foreign) luns. (i.e. improper storagegroup configuration)</description>
      <pubDate>Wed, 17 Aug 2005 10:48:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604629#M233477</guid>
      <dc:creator>Florian Heigl (new acc)</dc:creator>
      <dc:date>2005-08-17T10:48:24Z</dc:date>
    </item>
    <item>
      <title>Re: Normal for /sbin/bcheckrc to take long time at boot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604630#M233478</link>
      <description>I have been battleing the exact same problem on newly installed equipment since last May. VG activation of EMC DX500/DX700 luns is very slow. EMC came out with a patch for Powerpath, 4.3.1.2, but it did not resolve the issue for me. Many other HP/UX customers are reporting the same issue. I would log a ticket with EMC so we can turn up the heat on them and het this fixed.</description>
      <pubDate>Sun, 28 Aug 2005 09:55:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/normal-for-sbin-bcheckrc-to-take-long-time-at-boot/m-p/3604630#M233478</guid>
      <dc:creator>Mark Fisher_4</dc:creator>
      <dc:date>2005-08-28T09:55:41Z</dc:date>
    </item>
  </channel>
</rss>

