<?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: BAD BLOCKS in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848023#M612019</link>
    <description>Sorry, I forgot;&lt;BR /&gt;&lt;BR /&gt;If the condition I just talked about happens you will not find any bad blocks on your LV because the array already handled it. Your data block has been moved however so that block would be empty.&lt;BR /&gt;&lt;BR /&gt;David</description>
    <pubDate>Tue, 22 Aug 2006 08:58:44 GMT</pubDate>
    <dc:creator>David Child_1</dc:creator>
    <dc:date>2006-08-22T08:58:44Z</dc:date>
    <item>
      <title>BAD BLOCKS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848017#M612013</link>
      <description>Good Morning!!!&lt;BR /&gt;&lt;BR /&gt;Environment 11.11&lt;BR /&gt;Database folks are complaining of BAD BLOCKS and they refreshed the database. from the OS side i recommended umounting and doing full fsck on the filesystem in question. Now the customer wants to know the root cause of the issue. lvdisplay, syslog dmesg are all clean. Anything else we can check to provide the root cause for the BAD BLOCKS that oracle experienced?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Brian</description>
      <pubDate>Tue, 22 Aug 2006 07:56:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848017#M612013</guid>
      <dc:creator>brian_31</dc:creator>
      <dc:date>2006-08-22T07:56:00Z</dc:date>
    </item>
    <item>
      <title>Re: BAD BLOCKS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848018#M612014</link>
      <description>Brian,&lt;BR /&gt;anything showing with:&lt;BR /&gt;diskinfo -v /dev/rdsk/cxtxdx&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 22 Aug 2006 08:03:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848018#M612014</guid>
      <dc:creator>Peter Godron</dc:creator>
      <dc:date>2006-08-22T08:03:53Z</dc:date>
    </item>
    <item>
      <title>Re: BAD BLOCKS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848019#M612015</link>
      <description>Do you looking BAD BLOCKS on local disks or SAN disks? &lt;BR /&gt;&lt;BR /&gt;If you looking for Local then you can check using dd command or ask hp and they can give a binary program which checks bad blocks and also it may be fixed.&lt;BR /&gt;&lt;BR /&gt;dd if=/dev/rdsk/cXtYdZ of=/dev/null bs=4096k&lt;BR /&gt;&lt;BR /&gt;If it is SAN disk then talk to the Vendor.</description>
      <pubDate>Tue, 22 Aug 2006 08:13:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848019#M612015</guid>
      <dc:creator>IT_2007</dc:creator>
      <dc:date>2006-08-22T08:13:06Z</dc:date>
    </item>
    <item>
      <title>Re: BAD BLOCKS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848020#M612016</link>
      <description>issue the following command on the suspect PV and you should be getting an o/p similar to the one below on a good disk !!&lt;BR /&gt;&lt;BR /&gt;# echo 2400?20X|adb /dev/dsk/c2t0d0&lt;BR /&gt;2400:           44454645        43543031        0               0&lt;BR /&gt;                0               0               0               0&lt;BR /&gt;                0               0               0               0&lt;BR /&gt;                0               0               0               0&lt;BR /&gt;                0               0               0               0&lt;BR /&gt;#&lt;BR /&gt;&lt;BR /&gt;dd on a failed disk will hang for ever!!&lt;BR /&gt;</description>
      <pubDate>Tue, 22 Aug 2006 08:27:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848020#M612016</guid>
      <dc:creator>Pupil_1</dc:creator>
      <dc:date>2006-08-22T08:27:00Z</dc:date>
    </item>
    <item>
      <title>Re: BAD BLOCKS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848021#M612017</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Oracle will probably not tolerate OS bad block relocation.&lt;BR /&gt;&lt;BR /&gt;This is an oracle issue and the database may need to be restored from backup.&lt;BR /&gt;&lt;BR /&gt;If you have archive logging turned on there should not be much data loss.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 22 Aug 2006 08:47:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848021#M612017</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-08-22T08:47:56Z</dc:date>
    </item>
    <item>
      <title>Re: BAD BLOCKS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848022#M612018</link>
      <description>Brian,&lt;BR /&gt;&lt;BR /&gt;Is this connected to some type of disk array such as an EMC Symmetrix? Most modern arrays will handle bad block relocation at the hardware level. If you have BB relocation set on an LV and the array detects and moves the block there will be problems. Basically LVM moves the block as does the array so now you have a lost block.&lt;BR /&gt;&lt;BR /&gt;The last time I ran into this the DBAs had to do some recovery. For any LV's built on EMC Symmetrix LUNs you should have BB relocation set to NONE (lvchange -r N /dev/&lt;VG&gt;/&lt;LV&gt;).&lt;BR /&gt;&lt;BR /&gt;I'm sure other arrays (Hitachi, etc.) are similar.&lt;BR /&gt;&lt;BR /&gt;David&lt;/LV&gt;&lt;/VG&gt;</description>
      <pubDate>Tue, 22 Aug 2006 08:57:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848022#M612018</guid>
      <dc:creator>David Child_1</dc:creator>
      <dc:date>2006-08-22T08:57:05Z</dc:date>
    </item>
    <item>
      <title>Re: BAD BLOCKS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848023#M612019</link>
      <description>Sorry, I forgot;&lt;BR /&gt;&lt;BR /&gt;If the condition I just talked about happens you will not find any bad blocks on your LV because the array already handled it. Your data block has been moved however so that block would be empty.&lt;BR /&gt;&lt;BR /&gt;David</description>
      <pubDate>Tue, 22 Aug 2006 08:58:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848023#M612019</guid>
      <dc:creator>David Child_1</dc:creator>
      <dc:date>2006-08-22T08:58:44Z</dc:date>
    </item>
    <item>
      <title>Re: BAD BLOCKS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848024#M612020</link>
      <description>Thanks. is there a command to check the current bad block allocation, so that once i know i can run the lvchange -r to allocate it to none or what is the default?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Brian</description>
      <pubDate>Tue, 22 Aug 2006 09:22:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848024#M612020</guid>
      <dc:creator>brian_31</dc:creator>
      <dc:date>2006-08-22T09:22:20Z</dc:date>
    </item>
    <item>
      <title>Re: BAD BLOCKS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848025#M612021</link>
      <description>I'm not sure if I follow what you are asking at this point. The default is 'on'. You will want to set it for the array you are connected to. What array are you using?&lt;BR /&gt;&lt;BR /&gt;For Symmetrix it needs to be set to NONE (lvchange -r N /dev/&lt;VG&gt;/&lt;LV&gt;). It will show up in lvdisplay as "Bad block  NONE".&lt;BR /&gt;&lt;BR /&gt;From the lvchange man page:&lt;BR /&gt;&lt;BR /&gt;"-r N    Disable bad block relocation and the Bad Block Directory.  Upon a media failure, LVM will NOT attempt to relocate the bad block. In addition it will NOT enter the block in the Bad Block Directory. LVM will have no record of the block being bad, and will attempt to access it on future I/O requests."&lt;BR /&gt;&lt;BR /&gt;This way the array can handle any bad blocks and present only good blocks to the host.&lt;BR /&gt;&lt;BR /&gt;David&lt;/LV&gt;&lt;/VG&gt;</description>
      <pubDate>Tue, 22 Aug 2006 14:17:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848025#M612021</guid>
      <dc:creator>David Child_1</dc:creator>
      <dc:date>2006-08-22T14:17:42Z</dc:date>
    </item>
    <item>
      <title>Re: BAD BLOCKS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848026#M612022</link>
      <description>Brian,&lt;BR /&gt;&lt;BR /&gt;You can have bad blocks at two different levels, at the file system/hard drive level, and also at the Oracle level. Are the Oracle folks complaining of ORACLE BAD BLOCKS?  If so, they can verify the files and where the errors are with the "dbv" tool (from Oracle).  Syntax is :&lt;BR /&gt;&lt;BR /&gt;dbv BLOCKSIZE=[YOUR SIZE] FILE=[your file]&lt;BR /&gt;&lt;BR /&gt;e.g.&lt;BR /&gt;dbv BLOCKSIZE=8192 FILE=user01.dbf&lt;BR /&gt;&lt;BR /&gt;WARNING: THE ABOVE COMMAND IS *DBA FUNCTION* - not for sysadmin consumption!!!&lt;BR /&gt;&lt;BR /&gt;If this shows an error in a file, you can quickly determine if this is a UNIX issue by running a dd from the file to /dev/null:&lt;BR /&gt;dd if=user01.dbf of=/dev/null bs=8k&lt;BR /&gt;&lt;BR /&gt;If there is an error, it should give you an error in the same block as the Oracle error.  If it is clean from the dd command, it is very likely that this is an ORACLE ONLY problem, and really much to do with you (other than helping to restore if necessary).&lt;BR /&gt;&lt;BR /&gt;Have the dba's clarify how the BAD BLOCK is manifesting itself, and check it out a bit yourself.&lt;BR /&gt;&lt;BR /&gt;John</description>
      <pubDate>Tue, 22 Aug 2006 14:27:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848026#M612022</guid>
      <dc:creator>TwoProc</dc:creator>
      <dc:date>2006-08-22T14:27:32Z</dc:date>
    </item>
    <item>
      <title>Re: BAD BLOCKS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848027#M612023</link>
      <description>Hello Brian,&lt;BR /&gt;&lt;BR /&gt;I am not sure where your disks are connected to, either SAN or local internal disk?&lt;BR /&gt;&lt;BR /&gt;If it is a SAN disk it is recommended to turn off the bad block allocation on the logical system level. You SAN will manage bad block allocation by default.&lt;BR /&gt;&lt;BR /&gt;There are tools available (I am not sure who will supply either HP or SAN vendor) to check bad block reallocation on the logical volme level. &lt;BR /&gt;&lt;BR /&gt;To check bad blocks on the SAN, you have to contact your storage vendor to check it.&lt;BR /&gt;&lt;BR /&gt;Short and sweet, turn off bad block reallocation on the logical volume level if connected to SAN.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Sathish</description>
      <pubDate>Wed, 23 Aug 2006 03:33:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848027#M612023</guid>
      <dc:creator>sathish kannan</dc:creator>
      <dc:date>2006-08-23T03:33:21Z</dc:date>
    </item>
    <item>
      <title>Re: BAD BLOCKS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848028#M612024</link>
      <description>Hello,&lt;BR /&gt;maybe offtopic, but here is my ksh script for checking bad block setting:&lt;BR /&gt;&lt;BR /&gt;#!/usr/bin/ksh&lt;BR /&gt;# writed by Marek Mahut,&lt;BR /&gt;# This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY !&lt;BR /&gt;#&lt;BR /&gt;&lt;BR /&gt;echo "\nThis script show bad block settings for each LV: "&lt;BR /&gt;&lt;BR /&gt;ktosom=`/usr/bin/whoami`&lt;BR /&gt;if [[ $ktosom = "root" ]]; then&lt;BR /&gt;&lt;BR /&gt;getvgs=`ls -l /dev/*/group | awk '{print $10}' | sed 's/group//g'`&lt;BR /&gt;for var in $getvgs ; do&lt;BR /&gt;num=`ls -l $var | sort -i | awk '{print $10}' | grep "^lvol" | wc -l`&lt;BR /&gt;if [ $num -eq 0 ]; then&lt;BR /&gt;bla="blabla"&lt;BR /&gt;#echo "\n==&amp;gt;&amp;gt; VG $var has not logical volumes."&lt;BR /&gt;else&lt;BR /&gt;echo "\n==&amp;gt;  Logical volumes for VG $var: "&lt;BR /&gt;fi&lt;BR /&gt;volu=`ls -l $var | awk '{print $10}' | grep "^lvol" | sort -n`&lt;BR /&gt;for vat in $volu ; do&lt;BR /&gt;getsetting=`/usr/sbin/lvdisplay -v $var$vat | grep -i "bad block" | awk '{print $3}'`&lt;BR /&gt;echo "-&amp;gt; Bad block setting for $var$vat is set to \033[0;1;40;1m$getsetting\033[0m";&lt;BR /&gt;done&lt;BR /&gt;done&lt;BR /&gt;&lt;BR /&gt;else&lt;BR /&gt;echo "\n\033[1;37m\033[41m ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! \033[m"&lt;BR /&gt;echo "\033[1;37m\033[41m ! ! ! You are $ktosom, you don't have permissions to run this script  ! ! \033[m"&lt;BR /&gt;echo "\033[1;37m\033[41m ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! \033[m\n"&lt;BR /&gt;fi&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;echo "\nAnd have a nice day! :)"&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;all suggestions welcome :)&lt;BR /&gt;&lt;BR /&gt;Marek.</description>
      <pubDate>Wed, 23 Aug 2006 03:39:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bad-blocks/m-p/3848028#M612024</guid>
      <dc:creator>Marek Mahut</dc:creator>
      <dc:date>2006-08-23T03:39:23Z</dc:date>
    </item>
  </channel>
</rss>

