<?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: san disk space calculation in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660555#M242018</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;When OPEN-E emulation is selected than the default LUN Size you get will be exactly 13893MB. Allthough this can be altered as well and you can get the exact size of each LUN using "xpinfo -m" in the size column. Adding this space will give you the total space but there may be alternate paths for same LUNS. If you have one alternate path for each LUN than divide the total by two, if you have two alternate paths for each LUN then divide it by three and if you have three alternate paths then divide the total by four to get the effective space.&lt;BR /&gt;&lt;BR /&gt;Also if you have LUNs used in VxVM then you can use the following formula to find out the no. of alternate paths.&lt;BR /&gt;&lt;BR /&gt;#for i in `vxdisk list|awk '{print $1}'`&lt;BR /&gt;  do&lt;BR /&gt;  if [ $i != "DEVICE" ]&lt;BR /&gt;  then&lt;BR /&gt;  vxdmpadm getdmpnode nodename=$i&lt;BR /&gt;  fi&lt;BR /&gt;  done&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Devender</description>
    <pubDate>Sun, 30 Oct 2005 10:22:25 GMT</pubDate>
    <dc:creator>Devender Khatana</dc:creator>
    <dc:date>2005-10-30T10:22:25Z</dc:date>
    <item>
      <title>san disk space calculation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660550#M242013</link>
      <description>Dear Sirs,&lt;BR /&gt;&lt;BR /&gt;How to use "xpinfo -il" command to calculate the San Disk Space ?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Shiv</description>
      <pubDate>Sat, 29 Oct 2005 14:45:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660550#M242013</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2005-10-29T14:45:09Z</dc:date>
    </item>
    <item>
      <title>Re: san disk space calculation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660551#M242014</link>
      <description>Hi Shiv,&lt;BR /&gt;&lt;BR /&gt; "xpinfo -il" command can list you the number of LUNs assigned to the server.&lt;BR /&gt;You can redirect this o/p to a file.This itself will give you the device files for those LUNs.&lt;BR /&gt;--&amp;gt; xpinfo -il &amp;gt; /tmp/lun_check&lt;BR /&gt; Even you can furthur filter the device files like this:&lt;BR /&gt;&lt;BR /&gt;--&amp;gt;cat /tmp/lun_check |awk '{print N$}'&lt;BR /&gt;&lt;BR /&gt;If one/two luns you can doa diskinfo afterthat.Hope this can help.&lt;BR /&gt;&lt;BR /&gt;Regds, Granite</description>
      <pubDate>Sat, 29 Oct 2005 15:51:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660551#M242014</guid>
      <dc:creator>Granite</dc:creator>
      <dc:date>2005-10-29T15:51:09Z</dc:date>
    </item>
    <item>
      <title>Re: san disk space calculation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660552#M242015</link>
      <description>/dev/rdsk/c3t0d0        da  07  00  CL1H 0f:d4   OPEN-E           00010333&lt;BR /&gt;/dev/rdsk/c4t0d0        c5  17  00  CL2H 0f:d4   OPEN-E           00010333&lt;BR /&gt;&lt;BR /&gt;Someone said to count number of "OPEN-E"; divide by 2 and multiply by 14GB. This will give total San Disk Space.&lt;BR /&gt;&lt;BR /&gt;I am not sure how this formula works ?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Shiv&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 29 Oct 2005 17:20:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660552#M242015</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2005-10-29T17:20:19Z</dc:date>
    </item>
    <item>
      <title>Re: san disk space calculation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660553#M242016</link>
      <description>I guess&lt;BR /&gt;&lt;BR /&gt;xpinfo -m &lt;BR /&gt;&lt;BR /&gt;or &lt;BR /&gt;&lt;BR /&gt;xpinfo -p&lt;BR /&gt;&lt;BR /&gt;should give enough information regarding the size. See "man xpinfo" for more information,.</description>
      <pubDate>Sat, 29 Oct 2005 17:39:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660553#M242016</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2005-10-29T17:39:58Z</dc:date>
    </item>
    <item>
      <title>Re: san disk space calculation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660554#M242017</link>
      <description>Shiv,&lt;BR /&gt;&lt;BR /&gt;The person who told you this formula made an assumtion and an approximation.&lt;BR /&gt;&lt;BR /&gt;each OPEN-E volume is roughly 13.5 GB big. And the assumption mad is that you have an alternate path. So, if you have two fiber optic interfaces going to the xp disk array, then run the command :&lt;BR /&gt;&lt;BR /&gt;ioscan -fnC disk | grep "OPEN-E" | wc -l&lt;BR /&gt;&lt;BR /&gt;divide the number into two. this will give you the number of LUNs connected to one of the interfaces, the other is the alternate path and redundant, count-wise.&lt;BR /&gt;&lt;BR /&gt;multiply this number with 13.5 to get the SAN space in GBs.&lt;BR /&gt;&lt;BR /&gt;As a matter of fact, run a diskinfo against the /dev/rdsk/cxtxdx devices of one of the OPEN-E devices and get the exact size and use that for exact calculation if you wish. There is no magic about it.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;</description>
      <pubDate>Sun, 30 Oct 2005 01:25:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660554#M242017</guid>
      <dc:creator>Mel Burslan</dc:creator>
      <dc:date>2005-10-30T01:25:10Z</dc:date>
    </item>
    <item>
      <title>Re: san disk space calculation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660555#M242018</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;When OPEN-E emulation is selected than the default LUN Size you get will be exactly 13893MB. Allthough this can be altered as well and you can get the exact size of each LUN using "xpinfo -m" in the size column. Adding this space will give you the total space but there may be alternate paths for same LUNS. If you have one alternate path for each LUN than divide the total by two, if you have two alternate paths for each LUN then divide it by three and if you have three alternate paths then divide the total by four to get the effective space.&lt;BR /&gt;&lt;BR /&gt;Also if you have LUNs used in VxVM then you can use the following formula to find out the no. of alternate paths.&lt;BR /&gt;&lt;BR /&gt;#for i in `vxdisk list|awk '{print $1}'`&lt;BR /&gt;  do&lt;BR /&gt;  if [ $i != "DEVICE" ]&lt;BR /&gt;  then&lt;BR /&gt;  vxdmpadm getdmpnode nodename=$i&lt;BR /&gt;  fi&lt;BR /&gt;  done&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Devender</description>
      <pubDate>Sun, 30 Oct 2005 10:22:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660555#M242018</guid>
      <dc:creator>Devender Khatana</dc:creator>
      <dc:date>2005-10-30T10:22:25Z</dc:date>
    </item>
    <item>
      <title>Re: san disk space calculation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660556#M242019</link>
      <description>I also saw some description in the output of "xpinfo -il" as below:&lt;BR /&gt;&lt;BR /&gt;OPEN-E-CVS-CM&lt;BR /&gt;&lt;BR /&gt;Should we also count them for disk space calculation ?&lt;BR /&gt;&lt;BR /&gt;"OPEN-E-CVS-CM" stands for what ?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 30 Oct 2005 16:12:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660556#M242019</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2005-10-30T16:12:08Z</dc:date>
    </item>
    <item>
      <title>Re: san disk space calculation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660557#M242020</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;OPEN-E-CVS-CM represents "Custom Volume Size". It is some custom size LUN usually 100MB. These are configured if  you do not want to have the LUNs of default sizes.&lt;BR /&gt;&lt;BR /&gt;These LUNs shall be also counted as allocated disk space allthough are generally used for rootdg because if you use VxVM you should allocated atleast one device for rootdg. On systems running OS under LVM , the space allocated to rootdg is waste but is required. So we generally create a CVS volume to reduce the waste disk space. (Generally 100 MB is wasted as compared to 13893MB.)&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Devender&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Devender</description>
      <pubDate>Sun, 30 Oct 2005 20:35:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660557#M242020</guid>
      <dc:creator>Devender Khatana</dc:creator>
      <dc:date>2005-10-30T20:35:59Z</dc:date>
    </item>
    <item>
      <title>Re: san disk space calculation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660558#M242021</link>
      <description>Shivkumar,&lt;BR /&gt;&lt;BR /&gt;#!/bin/ksh&lt;BR /&gt;&lt;BR /&gt;XPSERIAL=&lt;REPLACE w=""&gt;&lt;/REPLACE&gt;xpinfo -i &amp;gt;/tmp/xpinfo&lt;BR /&gt;for culdev in `grep $XPSERIAL /tmp/xpinfo |awk '{print $6}'|sort|uniq`;do&lt;BR /&gt;  HPDEV=`grep $culdev /tmp/xpinfo|awk 'NR==1 {print $1}'`&lt;BR /&gt;  SIZE=`diskinfo $HPDEV | grep -i size|awk '{print $2}'`&lt;BR /&gt;  echo $HPDEV  $culdev $SIZE&lt;BR /&gt;done&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Just sum up the sizes (in KB)...&lt;BR /&gt;</description>
      <pubDate>Mon, 31 Oct 2005 09:26:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660558#M242021</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2005-10-31T09:26:46Z</dc:date>
    </item>
    <item>
      <title>Re: san disk space calculation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660559#M242022</link>
      <description>Oh btw, above script accurately portrays to you capacity of the currently presented XP San storage to the server you're running on regardless of:&lt;BR /&gt;&lt;BR /&gt;1.) emulation &lt;BR /&gt;2.) however many paths each LDEV/LUN is presented.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 31 Oct 2005 09:34:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660559#M242022</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2005-10-31T09:34:32Z</dc:date>
    </item>
    <item>
      <title>Re: san disk space calculation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660560#M242023</link>
      <description>Dear Sirs,&lt;BR /&gt;&lt;BR /&gt;How to figure out used and free disk space in SAN enabled disks on the server ?&lt;BR /&gt;&lt;BR /&gt;Whether SAN enabled and Direct attached disks co-exist ? If yes then how to differentiate them ?&lt;BR /&gt;&lt;BR /&gt;Appreciate your help.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Shiv</description>
      <pubDate>Tue, 15 Nov 2005 18:32:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660560#M242023</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2005-11-15T18:32:50Z</dc:date>
    </item>
    <item>
      <title>Re: san disk space calculation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660561#M242024</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;For counting the allocated and unused SAN space in a system, you should find the used and unused SAN LUNs in that system. Total LUNs assigned to VG's / DG's shall be considered as used space and unallocated space shall be free space.&lt;BR /&gt;&lt;BR /&gt;Yes, both can co exist in a system. SAN LUNs will show the enclosure name or emulation in ioscan whereas local disk and JBOD disks will show the disk model names in ioscan.&lt;BR /&gt;&lt;BR /&gt;For ex.&lt;BR /&gt;dev1:/home/hp&amp;gt;&amp;gt;ioscan -fnC disk&lt;BR /&gt;Class     I  H/W Path       Driver   S/W State   H/W Type     Description&lt;BR /&gt;==========================================================================&lt;BR /&gt;disk      0  0/0/1/1.2.0    sdisk    CLAIMED     DEVICE       HP 36.4GST336753LC&lt;BR /&gt;                           /dev/dsk/c1t2d0   /dev/rdsk/c1t2d0&lt;BR /&gt;disk      1  0/0/2/0.2.0    sdisk    CLAIMED     DEVICE       HP 36.4GST336753LC&lt;BR /&gt;                           /dev/dsk/c2t2d0   /dev/rdsk/c2t2d0&lt;BR /&gt;disk      2  0/0/2/1.2.0    sdisk    CLAIMED     DEVICE       HP      DVD-ROM 305&lt;BR /&gt;                           /dev/dsk/c3t2d0   /dev/rdsk/c3t2d0&lt;BR /&gt;disk      3  0/4/0/0.8.0.2.0.0.0   sdisk    CLAIMED     DEVICE       HP      OPEN-E&lt;BR /&gt;                           /dev/dsk/c4t0d0   /dev/rdsk/c4t0d0&lt;BR /&gt;disk      4  0/4/0/0.8.0.2.0.0.1   sdisk    CLAIMED     DEVICE       HP      OPEN-E&lt;BR /&gt;                           /dev/dsk/c4t0d1   /dev/rdsk/c4t0d1&lt;BR /&gt;disk      5  0/4/0/0.8.0.2.0.0.2   sdisk    CLAIMED     DEVICE       HP      OPEN-E&lt;BR /&gt;                           /dev/dsk/c4t0d2   /dev/rdsk/c4t0d2&lt;BR /&gt;disk      6  0/4/0/0.8.0.2.0.0.3   sdisk    CLAIMED     DEVICE       HP      OPEN-E&lt;BR /&gt;                           /dev/dsk/c4t0d3   /dev/rdsk/c4t0d3&lt;BR /&gt;disk      7  0/4/0/0.8.0.2.0.0.4   sdisk    CLAIMED     DEVICE       HP      OPEN-E&lt;BR /&gt;                           /dev/dsk/c4t0d4   /dev/rdsk/c4t0d4&lt;BR /&gt;disk      8  0/4/0/0.8.0.2.0.0.5   sdisk    CLAIMED     DEVICE       HP      OPEN-E&lt;BR /&gt;                           /dev/dsk/c4t0d5   /dev/rdsk/c4t0d5&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Here first two disks are locally attached, third is a DVD-ROM and later ones are LUNs of a storage.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Devender</description>
      <pubDate>Wed, 16 Nov 2005 10:36:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660561#M242024</guid>
      <dc:creator>Devender Khatana</dc:creator>
      <dc:date>2005-11-16T10:36:48Z</dc:date>
    </item>
    <item>
      <title>Re: san disk space calculation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660562#M242025</link>
      <description>Thanks a lot Devender for helping me out!!&lt;BR /&gt;&lt;BR /&gt;Shiv</description>
      <pubDate>Wed, 16 Nov 2005 12:21:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660562#M242025</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2005-11-16T12:21:28Z</dc:date>
    </item>
    <item>
      <title>Re: san disk space calculation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660563#M242026</link>
      <description>I used below command to find disk detail but got the error as shown below:-&lt;BR /&gt;&lt;BR /&gt;# diskinfo -b /dev/dsk/c8t12d0&lt;BR /&gt;diskinfo: can't open /dev/dsk/c8t12d0: Invalid argument&lt;BR /&gt;#&lt;BR /&gt;&lt;BR /&gt;and &lt;BR /&gt;# diskinfo -v /dev/dsk/c8t12d0&lt;BR /&gt;diskinfo: can't open /dev/dsk/c8t12d0: Invalid argument&lt;BR /&gt;#&lt;BR /&gt;&lt;BR /&gt;Appreciate any suggestion.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Shiv&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 16 Nov 2005 12:58:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660563#M242026</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2005-11-16T12:58:20Z</dc:date>
    </item>
    <item>
      <title>Re: san disk space calculation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660564#M242027</link>
      <description>Hi Shiv,&lt;BR /&gt;&lt;BR /&gt;You shall be using charater device here&lt;BR /&gt;#diskinfo -b /dev/rdsk/cxtydz&lt;BR /&gt;or &lt;BR /&gt;diskinfo -v /dev/rdsk/cxtydz&lt;BR /&gt;&lt;BR /&gt;Notice that rdsk instead of dsk.&lt;BR /&gt;&lt;BR /&gt;Allthough the error still shall not be this. Try this and revert.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Devender</description>
      <pubDate>Wed, 16 Nov 2005 13:13:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660564#M242027</guid>
      <dc:creator>Devender Khatana</dc:creator>
      <dc:date>2005-11-16T13:13:35Z</dc:date>
    </item>
    <item>
      <title>Re: san disk space calculation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660565#M242028</link>
      <description>You need to use the "r" device file&lt;BR /&gt;&lt;BR /&gt;diskinfo -v /dev/rdsk/c8t12d0&lt;BR /&gt;&lt;BR /&gt;In case ioscan is showing DISK-SUBSYSTEM for this device, you won't get a size information.</description>
      <pubDate>Wed, 16 Nov 2005 13:16:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/san-disk-space-calculation/m-p/3660565#M242028</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2005-11-16T13:16:15Z</dc:date>
    </item>
  </channel>
</rss>

