<?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: HPUX/Suse Cross Reference?  Where is rmsf? in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009874#M28512</link>
    <description>it looks like there were some EMC disk whihc were present earlier is not visible now.&lt;BR /&gt;&lt;BR /&gt;What is the linux verison? whihc EMC s/w do u use to manage the emc disk, like power path?. Did u reinstall it ?</description>
    <pubDate>Sat, 02 Jun 2007 13:49:09 GMT</pubDate>
    <dc:creator>skt_skt</dc:creator>
    <dc:date>2007-06-02T13:49:09Z</dc:date>
    <item>
      <title>HPUX/Suse Cross Reference?  Where is rmsf?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009861#M28499</link>
      <description>Is there a Linux equivalent to HP's "rmsf" command (and it's contemporaries)?  I'm running SLES9.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 30 May 2007 09:09:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009861#M28499</guid>
      <dc:creator>Craig Johnson_1</dc:creator>
      <dc:date>2007-05-30T09:09:20Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX/Suse Cross Reference?  Where is rmsf?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009862#M28500</link>
      <description>There is no rmsf equivalent in Linux. Most devices are managed dinamically. What do you need to do?</description>
      <pubDate>Wed, 30 May 2007 10:31:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009862#M28500</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2007-05-30T10:31:46Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX/Suse Cross Reference?  Where is rmsf?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009863#M28501</link>
      <description>We are trying to clean up after moving EMC BCV's to another cluster.  What happens after you do this is that commands such as vgs report problems - problems we'd rather not see, because they break our automation.&lt;BR /&gt;</description>
      <pubDate>Wed, 30 May 2007 10:47:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009863#M28501</guid>
      <dc:creator>Craig Johnson_1</dc:creator>
      <dc:date>2007-05-30T10:47:37Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX/Suse Cross Reference?  Where is rmsf?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009864#M28502</link>
      <description>If your problem is with volume groups reports, use the vgexport command to remove the volume groups configuration from the system.</description>
      <pubDate>Wed, 30 May 2007 10:58:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009864#M28502</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2007-05-30T10:58:20Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX/Suse Cross Reference?  Where is rmsf?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009865#M28503</link>
      <description>Here's an example.&lt;BR /&gt;&lt;BR /&gt;# vgs&lt;BR /&gt;  /dev/emcpowerfu: open failed: No such device or address&lt;BR /&gt;  /dev/emcpowerfv: open failed: No such device or address&lt;BR /&gt;  /dev/emcpowerfw: open failed: No such device or address&lt;BR /&gt;  /dev/emcpowerfs: open failed: No such device or address&lt;BR /&gt;  /dev/emcpowerft: open failed: No such device or address&lt;BR /&gt;  VG    #PV #LV #SN Attr  VSize   VFree  &lt;BR /&gt;  vg00    1   9   0 wz--n  60.31G  13.31G&lt;BR /&gt;  vg201   2   1   0 wz--n  17.00G   1.00G&lt;BR /&gt;  vg202   6   1   0 wz--n  51.00G   3.00G&lt;BR /&gt;  vg203   1   1   0 wz--n   8.50G   4.50G&lt;BR /&gt;  vg205   1   3   0 wz--n   8.50G   1.50G&lt;BR /&gt;  vg48    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg49    5   8   0 wz--n 306.34G  90.34G&lt;BR /&gt;  vg50    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg51    2   3   0 wz--n 102.11G  46.11G&lt;BR /&gt;  vg52    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg53    2   3   0 wz--n 102.11G  46.11G&lt;BR /&gt;  vg54    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg55    1   4   0 wz--n  68.08G  12.08G&lt;BR /&gt;  vg56    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg57    5   8   0 wz--n 306.34G  74.34G&lt;BR /&gt;  vg58    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg59    2   5   0 wz--n 102.11G  30.11G&lt;BR /&gt;  vg60    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg61    2   5   0 wz--n 102.11G  30.11G&lt;BR /&gt;  vg62    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg63    1   4   0 wz--n  68.08G  12.08G&lt;BR /&gt;  vg64    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg65    2   5   0 wz--n 102.11G  30.11G&lt;BR /&gt;  vg66    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg67    2   4   0 wz--n 136.16G  32.16G&lt;BR /&gt;  vg68    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg69    2   5   0 wz--n 102.11G  30.11G&lt;BR /&gt;  vg70    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg71    2   4   0 wz--n 136.16G  48.16G&lt;BR /&gt;  vg72    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg73    2   3   0 wz--n 102.11G  46.11G&lt;BR /&gt;  vg74    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg75    2   4   0 wz--n 136.16G  48.16G&lt;BR /&gt;  vg76    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg77    1   3   0 wz--n  34.03G  10.03G&lt;BR /&gt;  vg78    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg79    1   3   0 wz--n  34.03G  10.03G&lt;BR /&gt;  vg80    1   1   0 wz--n  34.03G   2.03G&lt;BR /&gt;  vg81    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg82    1   4   0 wz--n  34.03G   2.03G&lt;BR /&gt;  vg83    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg84    1   4   0 wz--n  34.03G   2.03G&lt;BR /&gt;  vg85    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg86    1   4   0 wz--n  34.03G   2.03G&lt;BR /&gt;  vg87    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg88    1   4   0 wz--n  34.03G   2.03G&lt;BR /&gt;  vg89    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;  vg90    1   4   0 wz--n  34.03G   2.03G&lt;BR /&gt;  vg91    1   1   0 wz--n   8.50G 512.00M&lt;BR /&gt;</description>
      <pubDate>Wed, 30 May 2007 11:44:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009865#M28503</guid>
      <dc:creator>Craig Johnson_1</dc:creator>
      <dc:date>2007-05-30T11:44:03Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX/Suse Cross Reference?  Where is rmsf?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009866#M28504</link>
      <description>Hi Craiq,&lt;BR /&gt;&lt;BR /&gt;since you have SLES9 have a look at&lt;BR /&gt;/bin/rescan-scsi-bus.sh&lt;BR /&gt;from&lt;BR /&gt;# rpm -qf /bin/rescan-scsi-bus.sh&lt;BR /&gt;scsi-1.7_2.36_1.16_0.11-0.4&lt;BR /&gt;&lt;BR /&gt;maybe you have to adjust some &lt;BR /&gt;'seq 0 7' expressions to scan a wider range.&lt;BR /&gt;&lt;BR /&gt;rgds&lt;BR /&gt;HGH&lt;BR /&gt;</description>
      <pubDate>Thu, 31 May 2007 02:18:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009866#M28504</guid>
      <dc:creator>Hemmetter</dc:creator>
      <dc:date>2007-05-31T02:18:31Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX/Suse Cross Reference?  Where is rmsf?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009867#M28505</link>
      <description>These are not on a SCSI bus, they are SAN attached disks (fiber channel).  I'm not sure what that bus scan is going to buy me?</description>
      <pubDate>Thu, 31 May 2007 07:54:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009867#M28505</guid>
      <dc:creator>Craig Johnson_1</dc:creator>
      <dc:date>2007-05-31T07:54:46Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX/Suse Cross Reference?  Where is rmsf?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009868#M28506</link>
      <description>Hi there.&lt;BR /&gt;Perhaps this link is useful for you :&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://networking.ringofsaturn.com/Unix/unixguide.php" target="_blank"&gt;http://networking.ringofsaturn.com/Unix/unixguide.php&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Unix commands in different systems&lt;BR /&gt;Rgds&lt;BR /&gt;Alexander M. Ermes</description>
      <pubDate>Thu, 31 May 2007 08:33:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009868#M28506</guid>
      <dc:creator>Alexander M. Ermes</dc:creator>
      <dc:date>2007-05-31T08:33:28Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX/Suse Cross Reference?  Where is rmsf?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009869#M28507</link>
      <description>Hi Craig,&lt;BR /&gt;&lt;BR /&gt;it doesnt matter if it is "real" SCSI or fibre channel. Fibre is just the "transport medium" for SCSI-commands.&lt;BR /&gt;&lt;BR /&gt;With output of lsscsi/inq.linux and  &lt;BR /&gt;rescan-scsi-bus.sh you can selectivly delete &lt;BR /&gt;some DSFs.&lt;BR /&gt;&lt;BR /&gt;rgds&lt;BR /&gt;HGH</description>
      <pubDate>Thu, 31 May 2007 08:34:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009869#M28507</guid>
      <dc:creator>Hemmetter</dc:creator>
      <dc:date>2007-05-31T08:34:27Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX/Suse Cross Reference?  Where is rmsf?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009870#M28508</link>
      <description>OK, thanks everyone.  Now, what is the difference between rmsf and just good old rm?</description>
      <pubDate>Thu, 31 May 2007 09:09:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009870#M28508</guid>
      <dc:creator>Craig Johnson_1</dc:creator>
      <dc:date>2007-05-31T09:09:53Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX/Suse Cross Reference?  Where is rmsf?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009871#M28509</link>
      <description>insf/rmsf can also manipulate HP-UX's list of currently-active devices, as well as operate on HP hardware paths and entire device classes. rm just removes files on the filesystem.</description>
      <pubDate>Thu, 31 May 2007 10:09:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009871#M28509</guid>
      <dc:creator>Heironimus</dc:creator>
      <dc:date>2007-05-31T10:09:11Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX/Suse Cross Reference?  Where is rmsf?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009872#M28510</link>
      <description>Yet there is no equivalent in SLES?</description>
      <pubDate>Thu, 31 May 2007 10:46:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009872#M28510</guid>
      <dc:creator>Craig Johnson_1</dc:creator>
      <dc:date>2007-05-31T10:46:45Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX/Suse Cross Reference?  Where is rmsf?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009873#M28511</link>
      <description>There is no equivalent because Linux doesn't manage devices and drivers the same way that HP-UX does. If the only thing you need is to change files out under /dev, you can use the MAKEDEV script to create them and rm to remove them. If you need to do any of the other things that insf/rmsf/etc do then you'll have a different procedure to follow.&lt;BR /&gt;&lt;BR /&gt;Since the "open failed" messages look like they're devices from EMC's multipath software, you should probably make sure that there isn't any special EMC procedure before you manually remove device files.&lt;BR /&gt;</description>
      <pubDate>Thu, 31 May 2007 16:28:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009873#M28511</guid>
      <dc:creator>Heironimus</dc:creator>
      <dc:date>2007-05-31T16:28:34Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX/Suse Cross Reference?  Where is rmsf?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009874#M28512</link>
      <description>it looks like there were some EMC disk whihc were present earlier is not visible now.&lt;BR /&gt;&lt;BR /&gt;What is the linux verison? whihc EMC s/w do u use to manage the emc disk, like power path?. Did u reinstall it ?</description>
      <pubDate>Sat, 02 Jun 2007 13:49:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hpux-suse-cross-reference-where-is-rmsf/m-p/4009874#M28512</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2007-06-02T13:49:09Z</dc:date>
    </item>
  </channel>
</rss>

