<?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: Root Volume in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/root-volume/m-p/2720246#M642045</link>
    <description>I THINK the reason is something like this:&lt;BR /&gt;LVM is a driver that is part of the kernel.  The IPL (initial program loader) does not contain this driver so does not know about logical to physical extent mappings.  However it does know about HFS filesystems and logical volume spaces.&lt;BR /&gt;Therefore to boot the system off /stand/vmunix it needs to know the exact position on the boot disk that it is going to find the /stand filesystem and load the kernel file you specify, also to know that the filesystem is going to be on contiguous blocks of disk.&lt;BR /&gt;Swap needs to be contiguous for performance reasons and for the ability to use it as a DUMP area, simply writing memory pages to contiguous disk space using a simple algorithm when the system panics.&lt;BR /&gt;I think a lot of this may be historical.  &lt;BR /&gt;What I find interesting is that it is still  possible to boot HPUX specifying cXtYdZs1lvm or lvmdisk which means that there must be some knowledge of logical volumes in there somewhere.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 09 May 2002 07:35:34 GMT</pubDate>
    <dc:creator>Steve Lewis</dc:creator>
    <dc:date>2002-05-09T07:35:34Z</dc:date>
    <item>
      <title>Root Volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-volume/m-p/2720242#M642041</link>
      <description>Hi Intellects&lt;BR /&gt;&lt;BR /&gt;Can anyone explain, WHY ROOT VOLUMES SHOULD BE CONTIGUOUS?&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Noel Miranda</description>
      <pubDate>Thu, 09 May 2002 05:36:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-volume/m-p/2720242#M642041</guid>
      <dc:creator>Noel Miranda_1</dc:creator>
      <dc:date>2002-05-09T05:36:15Z</dc:date>
    </item>
    <item>
      <title>Re: Root Volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-volume/m-p/2720243#M642042</link>
      <description>Hi Noel,&lt;BR /&gt;&lt;BR /&gt;If a logical volume is to be used as either root, primary swap, dump or /stand the physical extents must be contiguous.This means that the physical extents of the disk must be allocated with no gaps on a single physical volume. One other reason is that BDRA (Boot Data Reserved Area) needs to be contiguous for booting kernels, saving crash dumps etc&lt;BR /&gt;&lt;BR /&gt;Hope this explains things.....&lt;BR /&gt;&lt;BR /&gt;Michael&lt;BR /&gt;</description>
      <pubDate>Thu, 09 May 2002 05:43:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-volume/m-p/2720243#M642042</guid>
      <dc:creator>Michael Tully</dc:creator>
      <dc:date>2002-05-09T05:43:36Z</dc:date>
    </item>
    <item>
      <title>Re: Root Volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-volume/m-p/2720244#M642043</link>
      <description>Michael,&lt;BR /&gt;&lt;BR /&gt;If a logical volume is to be used as either root, primary swap, dump or /stand the physical extents must be contiguous.This means that the physical extents of the disk must be allocated with no gaps on a single physical volume.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt; Why is this so??&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 09 May 2002 06:32:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-volume/m-p/2720244#M642043</guid>
      <dc:creator>Noel Miranda_1</dc:creator>
      <dc:date>2002-05-09T06:32:00Z</dc:date>
    </item>
    <item>
      <title>Re: Root Volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-volume/m-p/2720245#M642044</link>
      <description>Hi,&lt;BR /&gt;the root filesytem contains the kernel and other os files and root is the highest level filesystem. Since it has to be accessed fast without going through file system, hence it is contiguous</description>
      <pubDate>Thu, 09 May 2002 06:41:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-volume/m-p/2720245#M642044</guid>
      <dc:creator>Ravi_8</dc:creator>
      <dc:date>2002-05-09T06:41:34Z</dc:date>
    </item>
    <item>
      <title>Re: Root Volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-volume/m-p/2720246#M642045</link>
      <description>I THINK the reason is something like this:&lt;BR /&gt;LVM is a driver that is part of the kernel.  The IPL (initial program loader) does not contain this driver so does not know about logical to physical extent mappings.  However it does know about HFS filesystems and logical volume spaces.&lt;BR /&gt;Therefore to boot the system off /stand/vmunix it needs to know the exact position on the boot disk that it is going to find the /stand filesystem and load the kernel file you specify, also to know that the filesystem is going to be on contiguous blocks of disk.&lt;BR /&gt;Swap needs to be contiguous for performance reasons and for the ability to use it as a DUMP area, simply writing memory pages to contiguous disk space using a simple algorithm when the system panics.&lt;BR /&gt;I think a lot of this may be historical.  &lt;BR /&gt;What I find interesting is that it is still  possible to boot HPUX specifying cXtYdZs1lvm or lvmdisk which means that there must be some knowledge of logical volumes in there somewhere.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 09 May 2002 07:35:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-volume/m-p/2720246#M642045</guid>
      <dc:creator>Steve Lewis</dc:creator>
      <dc:date>2002-05-09T07:35:34Z</dc:date>
    </item>
    <item>
      <title>Re: Root Volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/root-volume/m-p/2720247#M642046</link>
      <description>hi,&lt;BR /&gt;The reason being to reduce the seek time for the disk access to load the processes like kernel /stand/vmunix , swapped processes without any delay.&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;U.SivaKumar</description>
      <pubDate>Thu, 09 May 2002 08:11:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/root-volume/m-p/2720247#M642046</guid>
      <dc:creator>U.SivaKumar_2</dc:creator>
      <dc:date>2002-05-09T08:11:06Z</dc:date>
    </item>
  </channel>
</rss>

