<?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: cross device link issue in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cross-device-link-issue/m-p/3922194#M609322</link>
    <description>0) make sure that the minor device numbers on all nodes are unique. It's ok to have the same minor device number (e.g.) 0x050000 for /dev/vg*/group on different nodes but there can be at most one 0x050000 any one node. Your first task is to do an ls -l /dev/vg*/group on all the nodes and make sure that there are no dupicate minor device numbers on a node. This can lead to extremely bizarre and chaotic behavior.&lt;BR /&gt;&lt;BR /&gt;1) Make sure that you do an ioscan -fn after connecting new disks and then do an insf to create the device nodes.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 11 Jan 2007 13:10:59 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2007-01-11T13:10:59Z</dc:date>
    <item>
      <title>cross device link issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cross-device-link-issue/m-p/3922191#M609319</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have two nodes running MC/SG connect to EMC Clariion.  I have a volume that I cannot mounted and I am getting the following error message.  This volume is using EMC snap view to create a snapshot from another VG.  I suspect it was due to snapshot the two VG has two same VGID that's why it cannot be mounted.  Any opinion.&lt;BR /&gt;&lt;BR /&gt;sm1a# vgchange -a e /dev/backupvg00&lt;BR /&gt;&lt;BR /&gt;vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c5t9d2":&lt;BR /&gt;&lt;BR /&gt;Cross-device link&lt;BR /&gt;&lt;BR /&gt;vgchange: Activation mode requested for the volume group "/dev/backupvg00" conflicts with configured mode.&lt;BR /&gt;&lt;BR /&gt;vgchange: Warning: couldn't query physical volume "/dev/dsk/c5t9d2":&lt;BR /&gt;&lt;BR /&gt;The specified path does not correspond to physical volume attached to &lt;BR /&gt;&lt;BR /&gt;this volume group&lt;BR /&gt;&lt;BR /&gt;vgchange: Warning: couldn't query all of the physical volumes.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Jan 2007 00:44:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cross-device-link-issue/m-p/3922191#M609319</guid>
      <dc:creator>kholikt</dc:creator>
      <dc:date>2007-01-08T00:44:28Z</dc:date>
    </item>
    <item>
      <title>Re: cross device link issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cross-device-link-issue/m-p/3922192#M609320</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;I've run into this with SG a few times. First make sure the snapshot operation is really done.&lt;BR /&gt;&lt;BR /&gt;Possible solutions:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.docs.hp.com/en/A3262-90051/A3262-90051.pdf" target="_blank"&gt;http://www.docs.hp.com/en/A3262-90051/A3262-90051.pdf&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1025950" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1025950&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1025994" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1025994&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1042689" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1042689&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I'm not sure I found the exact solution because the cause can be different. I recall a simple two step vgchange solution cleaning this up. It's probably in the pdf I posted first.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 08 Jan 2007 01:06:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cross-device-link-issue/m-p/3922192#M609320</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-01-08T01:06:04Z</dc:date>
    </item>
    <item>
      <title>Re: cross device link issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cross-device-link-issue/m-p/3922193#M609321</link>
      <description>see vgchid</description>
      <pubDate>Thu, 11 Jan 2007 12:23:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cross-device-link-issue/m-p/3922193#M609321</guid>
      <dc:creator>Kevin Wright</dc:creator>
      <dc:date>2007-01-11T12:23:39Z</dc:date>
    </item>
    <item>
      <title>Re: cross device link issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cross-device-link-issue/m-p/3922194#M609322</link>
      <description>0) make sure that the minor device numbers on all nodes are unique. It's ok to have the same minor device number (e.g.) 0x050000 for /dev/vg*/group on different nodes but there can be at most one 0x050000 any one node. Your first task is to do an ls -l /dev/vg*/group on all the nodes and make sure that there are no dupicate minor device numbers on a node. This can lead to extremely bizarre and chaotic behavior.&lt;BR /&gt;&lt;BR /&gt;1) Make sure that you do an ioscan -fn after connecting new disks and then do an insf to create the device nodes.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 11 Jan 2007 13:10:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cross-device-link-issue/m-p/3922194#M609322</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2007-01-11T13:10:59Z</dc:date>
    </item>
  </channel>
</rss>

