<?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: File system unmount--make it to mount in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688306#M617302</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Print the whole information related to /dev/dsk/c26t4d1 &amp;amp; /dev/dsk/c29t4d1.&lt;BR /&gt;&lt;BR /&gt;Also post&lt;BR /&gt;#diskinfo -v /dev/rdsk/c26t4d1&lt;BR /&gt;&lt;BR /&gt;&amp;amp;&lt;BR /&gt;&lt;BR /&gt;#diskinfo -v /dev/rdsk/c26t4d1&lt;BR /&gt;&lt;BR /&gt;Allthough this should not happen as you have alternate path to access the disk unless there is some problem at storage/SAN level.&lt;BR /&gt;&lt;BR /&gt;Was there something done/faced in storage at the same time?&lt;BR /&gt;&lt;BR /&gt;If the output of the diskinfo shows the disk as healthy. You can reactivate VG and then the disk should become available if it is really available.&lt;BR /&gt;&lt;BR /&gt;#vgchange -a y /dev/vg73&lt;BR /&gt;&lt;BR /&gt;Then retry mount and if required fsck.&lt;BR /&gt;&lt;BR /&gt;Allthough there may be some corruption to data in such scenarions and you should be able to find that in fsck errors if any.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Devender</description>
    <pubDate>Sun, 11 Dec 2005 10:58:55 GMT</pubDate>
    <dc:creator>Devender Khatana</dc:creator>
    <dc:date>2005-12-11T10:58:55Z</dc:date>
    <item>
      <title>File system unmount--make it to mount</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688298#M617294</link>
      <description>Hi guys,&lt;BR /&gt;My two file systems are unmounted now.&lt;BR /&gt;and when i tring to mount..&lt;BR /&gt;this is the error:&lt;BR /&gt;&lt;BR /&gt;# mount -F vxfs /dev/vg73/ORACBPD_data_dat01 /ACBP/db/ORACBPD/data/dat01&lt;BR /&gt;mount: /ACBP/db/ORACBPD/data/dat01: I/O error&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;# umount /ACBP/db/ORACBPD/data/idx01&lt;BR /&gt;# mount -F vxfs /dev/vg73/ORACBPD_data_idx01 /ACBP/db/ORACBPD/data/idx01&lt;BR /&gt;vxfs mount: read of super-block on /dev/vg73/ORACBPD_data_idx01 failed: I/O error&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;bdf: /ACBP/db/ORACBPD/data/dat01: I/O error&lt;BR /&gt;&lt;BR /&gt;#cd /ACBP/db/ORACBPD/data&lt;BR /&gt;&lt;BR /&gt;# ll&lt;BR /&gt;./dat01 not found&lt;BR /&gt;total 6&lt;BR /&gt;drwxr-xr-x   2 laoracle   LAdba           96 Nov 16 08:45 idx01&lt;BR /&gt;drwxr-xr-x   3 laoracle   LAdba           96 Nov 16 11:19 rbs01&lt;BR /&gt;drwxr-xr-x   3 laoracle   LAdba         1024 Nov 16 11:19 redoA&lt;BR /&gt;drwxr-xr-x   3 laoracle   LAdba         1024 Nov 16 11:19 redoB&lt;BR /&gt;drwxr-xr-x   3 laoracle   LAdba         1024 Nov 16 11:19 redoC&lt;BR /&gt;drwxr-xr-x   3 laoracle   LAdba           96 Nov 16 11:20 tmp01&lt;BR /&gt;&lt;BR /&gt;# fsck -y /dev/vg73/ORACBPD_data_idx01&lt;BR /&gt;vxfs fsck: read of super-block on /dev/vg73/ORACBPD_data_idx01 failed: I/O error&lt;BR /&gt;file system check failure, aborting ...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;# fsck -m -y /dev/vg73/ORACBPD_data_idx01&lt;BR /&gt;vxfs fsck: read of super-block on /dev/vg73/ORACBPD_data_idx01 failed: I/O error&lt;BR /&gt;&lt;BR /&gt;# fsck -F vxfs -m -y /dev/vg73/ORACBPD_data_idx01&lt;BR /&gt;vxfs fsck: read of super-block on /dev/vg73/ORACBPD_data_idx01 failed: I/O error&lt;BR /&gt;</description>
      <pubDate>Fri, 09 Dec 2005 07:16:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688298#M617294</guid>
      <dc:creator>Bunty..</dc:creator>
      <dc:date>2005-12-09T07:16:42Z</dc:date>
    </item>
    <item>
      <title>Re: File system unmount--make it to mount</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688299#M617295</link>
      <description>You have a failed disk. These are serious errors and cannot be fixed. fsck does not fix disk hardware failures, it only fixes simple directory and disk map mistakes. You'll have to replace the bad disk.</description>
      <pubDate>Fri, 09 Dec 2005 07:21:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688299#M617295</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-12-09T07:21:38Z</dc:date>
    </item>
    <item>
      <title>Re: File system unmount--make it to mount</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688300#M617296</link>
      <description>Dear Bunty,&lt;BR /&gt;&lt;BR /&gt;I feel the filesystem is currupt. Was there any abrupt shutdown ?&lt;BR /&gt;&lt;BR /&gt;Please do &lt;BR /&gt;#lvdisplay -v dev/vg73/ORACBPD_data_idx01&lt;BR /&gt;&lt;BR /&gt;and check for any stale extents.&lt;BR /&gt;&lt;BR /&gt;With Regards,&lt;BR /&gt;&lt;BR /&gt;Siva.</description>
      <pubDate>Fri, 09 Dec 2005 07:23:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688300#M617296</guid>
      <dc:creator>Sivakumar TS</dc:creator>
      <dc:date>2005-12-09T07:23:00Z</dc:date>
    </item>
    <item>
      <title>Re: File system unmount--make it to mount</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688301#M617297</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;These are symptoms of a failed disk. You should see some STALE PEs in the vgdisplay -v output for this VG. If this VG is not on locally attached disks and is access through SAN than there is a probably a cable fault.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Devender</description>
      <pubDate>Fri, 09 Dec 2005 07:26:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688301#M617297</guid>
      <dc:creator>Devender Khatana</dc:creator>
      <dc:date>2005-12-09T07:26:14Z</dc:date>
    </item>
    <item>
      <title>Re: File system unmount--make it to mount</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688302#M617298</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;When fsck has failed, you are done, disk replacement and data restore is your only option.&lt;BR /&gt;&lt;BR /&gt;You may want to see if you can lvremove the logical volume and vgreduce the disk out of the volume group, just to make the rebuild easier, but it probably will not work.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Fri, 09 Dec 2005 07:28:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688302#M617298</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2005-12-09T07:28:02Z</dc:date>
    </item>
    <item>
      <title>Re: File system unmount--make it to mount</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688303#M617299</link>
      <description>#lvdisplay -v dev/vg73/ORACBPD_data_idx01&lt;BR /&gt;all extents are OK.&lt;BR /&gt;is there may be some issue og PEs size.&lt;BR /&gt;PEs size is 4MB.&lt;BR /&gt;and this LV size is 31GB.&lt;BR /&gt;&lt;BR /&gt;--- Volume groups ---&lt;BR /&gt;VG Name                     /dev/vg73&lt;BR /&gt;VG Write Access             read/write&lt;BR /&gt;VG Status                   available&lt;BR /&gt;Max LV                      255&lt;BR /&gt;Cur LV                      9&lt;BR /&gt;Open LV                     9&lt;BR /&gt;Max PV                      16&lt;BR /&gt;Cur PV                      2&lt;BR /&gt;Act PV                      2&lt;BR /&gt;Max PE per PV               9727&lt;BR /&gt;VGDA                        4&lt;BR /&gt;PE Size (Mbytes)            4&lt;BR /&gt;Total PE                    19452&lt;BR /&gt;Alloc PE                    15875&lt;BR /&gt;Free PE                     3577&lt;BR /&gt;Total PVG                   0&lt;BR /&gt;Total Spare PVs             0&lt;BR /&gt;Total Spare PVs in use      0&lt;BR /&gt;&lt;BR /&gt;   --- Logical volumes ---&lt;BR /&gt;   LV Name                     /dev/vg73/ORACBPD_data_dat01&lt;BR /&gt;   LV Status                   available/syncd&lt;BR /&gt;   LV Size (Mbytes)            31000&lt;BR /&gt;   Current LE                  7750&lt;BR /&gt;   Allocated PE                7750&lt;BR /&gt;   Used PV                     1&lt;BR /&gt;&lt;BR /&gt;   LV Name                     /dev/vg73/ORACBPD_data_idx01&lt;BR /&gt;   LV Status                   available/syncd&lt;BR /&gt;   LV Size (Mbytes)            11000&lt;BR /&gt;   Current LE                  2750&lt;BR /&gt;   Allocated PE                2750&lt;BR /&gt;   Used PV                     2&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 09 Dec 2005 07:43:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688303#M617299</guid>
      <dc:creator>Bunty..</dc:creator>
      <dc:date>2005-12-09T07:43:29Z</dc:date>
    </item>
    <item>
      <title>Re: File system unmount--make it to mount</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688304#M617300</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Have you got some messages in the syslog.log while it got unmounted or in dmesg. I suspect a intermediant link failure. Is it on SAN or local disk?&lt;BR /&gt;&lt;BR /&gt;I think it is the best time to check both your disks in that VG for I/O errors through dd command.&lt;BR /&gt;&lt;BR /&gt;#dd if=/dev/rdsk/cxtydz of=/dev/null bs=2048k&lt;BR /&gt;&lt;BR /&gt;Repeat same for other disk in VG. The disk device file is not visible from the posts. so replace /dev/rdsk/cxtydz with that.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Devender</description>
      <pubDate>Fri, 09 Dec 2005 08:00:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688304#M617300</guid>
      <dc:creator>Devender Khatana</dc:creator>
      <dc:date>2005-12-09T08:00:26Z</dc:date>
    </item>
    <item>
      <title>Re: File system unmount--make it to mount</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688305#M617301</link>
      <description>it is connected to SAN.&lt;BR /&gt;&lt;BR /&gt;#vgdisplay -v /dev/vg73 | more&lt;BR /&gt;--- Physical volumes ---&lt;BR /&gt;PV Name /dev/dsk/c26t4d1&lt;BR /&gt;PV Name /dev/dsk/c29t4d1 Alternate Link&lt;BR /&gt;PV Status unavailable&lt;BR /&gt;Total PE 9726&lt;BR /&gt;Free PE 0&lt;BR /&gt;Autoswitch On&lt;BR /&gt;&lt;BR /&gt;PV Name /dev/dsk/c26t4d2&lt;BR /&gt;PV Name /dev/dsk/c29t4d2 Alternate Link&lt;BR /&gt;PV Status available&lt;BR /&gt;Total PE 9726&lt;BR /&gt;Free PE 3577&lt;BR /&gt;Autoswitch On&lt;BR /&gt;&lt;BR /&gt;how to make it available? &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;# ioscan -fnC disk | grep c26t4d1&lt;BR /&gt;/dev/dsk/c26t4d1 /dev/rdsk/c26t4d1&lt;BR /&gt;&lt;BR /&gt;# ioscan -fnC disk | grep c26t4d1&lt;BR /&gt;/dev/dsk/c26t4d1 /dev/rdsk/c26t4d1&lt;BR /&gt;&lt;BR /&gt;# ioscan -fnC disk | grep c26t4d2&lt;BR /&gt;/dev/dsk/c26t4d2 /dev/rdsk/c26t4d2&lt;BR /&gt;&lt;BR /&gt;# ioscan -fnC disk | grep c29t4d1&lt;BR /&gt;/dev/dsk/c29t4d1 /dev/rdsk/c29t4d1&lt;BR /&gt;&lt;BR /&gt;# ioscan -fnC disk | grep c29t4d2&lt;BR /&gt;/dev/dsk/c29t4d2 /dev/rdsk/c29t4d2&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;should i run this command:&lt;BR /&gt;#dd if=/dev/rdsk/c26t4d1 of=/dev/null bs=2048k&lt;BR /&gt;&lt;BR /&gt;will it make PV status abailable&lt;BR /&gt;</description>
      <pubDate>Fri, 09 Dec 2005 08:36:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688305#M617301</guid>
      <dc:creator>Bunty..</dc:creator>
      <dc:date>2005-12-09T08:36:24Z</dc:date>
    </item>
    <item>
      <title>Re: File system unmount--make it to mount</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688306#M617302</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Print the whole information related to /dev/dsk/c26t4d1 &amp;amp; /dev/dsk/c29t4d1.&lt;BR /&gt;&lt;BR /&gt;Also post&lt;BR /&gt;#diskinfo -v /dev/rdsk/c26t4d1&lt;BR /&gt;&lt;BR /&gt;&amp;amp;&lt;BR /&gt;&lt;BR /&gt;#diskinfo -v /dev/rdsk/c26t4d1&lt;BR /&gt;&lt;BR /&gt;Allthough this should not happen as you have alternate path to access the disk unless there is some problem at storage/SAN level.&lt;BR /&gt;&lt;BR /&gt;Was there something done/faced in storage at the same time?&lt;BR /&gt;&lt;BR /&gt;If the output of the diskinfo shows the disk as healthy. You can reactivate VG and then the disk should become available if it is really available.&lt;BR /&gt;&lt;BR /&gt;#vgchange -a y /dev/vg73&lt;BR /&gt;&lt;BR /&gt;Then retry mount and if required fsck.&lt;BR /&gt;&lt;BR /&gt;Allthough there may be some corruption to data in such scenarions and you should be able to find that in fsck errors if any.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Devender</description>
      <pubDate>Sun, 11 Dec 2005 10:58:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-unmount-make-it-to-mount/m-p/3688306#M617302</guid>
      <dc:creator>Devender Khatana</dc:creator>
      <dc:date>2005-12-11T10:58:55Z</dc:date>
    </item>
  </channel>
</rss>

