<?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: Create Disk Device Special File in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/create-disk-device-special-file/m-p/3539382#M222935</link>
    <description>Well, you could do an insf -C disk -e to restrict the device nodes to be added otherwise, insf -e will search for all device types. Either is considered to be a safe operation on a live system. No existing device nodes are removed.&lt;BR /&gt;&lt;BR /&gt;My approach for connecting a new disk to a live system would be this:&lt;BR /&gt;&lt;BR /&gt;add the disk (or LUN) &lt;BR /&gt;ioscan -fn&lt;BR /&gt;insf -e&lt;BR /&gt;&lt;BR /&gt;You should now be able to pvcreate or use the raw device and assuming the hardware is "hot-plug" there is no need to shutdown. &lt;BR /&gt;</description>
    <pubDate>Fri, 06 May 2005 10:12:10 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2005-05-06T10:12:10Z</dc:date>
    <item>
      <title>Create Disk Device Special File</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/create-disk-device-special-file/m-p/3539378#M222931</link>
      <description>I am going to be presenting some additional storage (virtual disk) to one of our HP-UX servers today.&lt;BR /&gt;&lt;BR /&gt;The notes from the previous admin state that one can create the disk device files with:&lt;BR /&gt;&lt;BR /&gt;insf -e&lt;BR /&gt;&lt;BR /&gt;I am wondering if the "-e" is necessary and whether a preferrable method for a live system is instead:&lt;BR /&gt;&lt;BR /&gt;insf -C disk&lt;BR /&gt;&lt;BR /&gt;A second question is whether the "-e" option would have disrupted active processes on the system.&lt;BR /&gt;&lt;BR /&gt;Goal: add disk, system live and active. How best to create device file?</description>
      <pubDate>Fri, 06 May 2005 10:02:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/create-disk-device-special-file/m-p/3539378#M222931</guid>
      <dc:creator>Adam Garsha</dc:creator>
      <dc:date>2005-05-06T10:02:09Z</dc:date>
    </item>
    <item>
      <title>Re: Create Disk Device Special File</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/create-disk-device-special-file/m-p/3539379#M222932</link>
      <description>There are no ill-effects from running insf -e - no active processes will be affected.  Usually the -e option is used simply because it's easier than figuring out the path to the particular disk - sheer laziness.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Fri, 06 May 2005 10:06:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/create-disk-device-special-file/m-p/3539379#M222932</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2005-05-06T10:06:40Z</dc:date>
    </item>
    <item>
      <title>Re: Create Disk Device Special File</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/create-disk-device-special-file/m-p/3539380#M222933</link>
      <description>You can run insf -e on live system without impacting anything.&lt;BR /&gt;If the kernel drivers are in place a fresh ioscan -fn should see your new disks after running insf -e&lt;BR /&gt;&lt;BR /&gt;-USA..</description>
      <pubDate>Fri, 06 May 2005 10:10:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/create-disk-device-special-file/m-p/3539380#M222933</guid>
      <dc:creator>Uday_S_Ankolekar</dc:creator>
      <dc:date>2005-05-06T10:10:41Z</dc:date>
    </item>
    <item>
      <title>Re: Create Disk Device Special File</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/create-disk-device-special-file/m-p/3539381#M222934</link>
      <description>I usually just do an 'insf -e'.  It may not be the best way, but it has always worked for me.&lt;BR /&gt;&lt;BR /&gt;No, I have never had a problem with 'insf -e' disrupting anything and I have done it on live production system numerous times, including yesterday.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 06 May 2005 10:11:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/create-disk-device-special-file/m-p/3539381#M222934</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2005-05-06T10:11:57Z</dc:date>
    </item>
    <item>
      <title>Re: Create Disk Device Special File</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/create-disk-device-special-file/m-p/3539382#M222935</link>
      <description>Well, you could do an insf -C disk -e to restrict the device nodes to be added otherwise, insf -e will search for all device types. Either is considered to be a safe operation on a live system. No existing device nodes are removed.&lt;BR /&gt;&lt;BR /&gt;My approach for connecting a new disk to a live system would be this:&lt;BR /&gt;&lt;BR /&gt;add the disk (or LUN) &lt;BR /&gt;ioscan -fn&lt;BR /&gt;insf -e&lt;BR /&gt;&lt;BR /&gt;You should now be able to pvcreate or use the raw device and assuming the hardware is "hot-plug" there is no need to shutdown. &lt;BR /&gt;</description>
      <pubDate>Fri, 06 May 2005 10:12:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/create-disk-device-special-file/m-p/3539382#M222935</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-05-06T10:12:10Z</dc:date>
    </item>
    <item>
      <title>Re: Create Disk Device Special File</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/create-disk-device-special-file/m-p/3539383#M222936</link>
      <description>P.S.  The procedure I usually go through is:&lt;BR /&gt;&lt;BR /&gt;1) Define LUNs on array and set up appropriate WWNs in LUN access table (we use a VA7400 with Secure Manager)&lt;BR /&gt;&lt;BR /&gt;2) Do an 'ioscan -fnC disk' to verify the machine can see the LUNs.&lt;BR /&gt;&lt;BR /&gt;3) Do an 'insf -e' to create /dev/dsk and /dev/rdsk files.&lt;BR /&gt;&lt;BR /&gt;4) Do an 'ioscan -fnC disk' again to verify /dev/dsk and /dev/rdsk files.&lt;BR /&gt;&lt;BR /&gt;5) Do whatever LVM (create or extend VGs and LVs) work is necesssary.</description>
      <pubDate>Fri, 06 May 2005 10:14:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/create-disk-device-special-file/m-p/3539383#M222936</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2005-05-06T10:14:22Z</dc:date>
    </item>
    <item>
      <title>Re: Create Disk Device Special File</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/create-disk-device-special-file/m-p/3539384#M222937</link>
      <description>As everybody says, insf -e has had no ill effects. No changes to the device names or service interruptions. You could be more specific and just run insf with the specific options for that device.&lt;BR /&gt;&lt;BR /&gt;Either way you will get you device files.</description>
      <pubDate>Fri, 06 May 2005 10:18:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/create-disk-device-special-file/m-p/3539384#M222937</guid>
      <dc:creator>Rick Garland</dc:creator>
      <dc:date>2005-05-06T10:18:56Z</dc:date>
    </item>
  </channel>
</rss>

