<?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: Distriputed LVM and striped LVM in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537787#M368928</link>
    <description>Hi Senthil:&lt;BR /&gt;&lt;BR /&gt;1.  The choices are made during your logical volume creation.  See the manpages for 'lvcreate'.&lt;BR /&gt;&lt;BR /&gt;2.  The purpose is to spread I/O across as many physical disk as possible to reduce disk queue lengths on any one device and load-level I/O.  You might think of distributed extents as very large stripes.  Two drawbacks to using either is if you need to grow your logical volume you must add physical volumes to its volume group in n-units where 'n' equals the number of physical volumes over which extents are spread.  In my opinion, with modern SAN farms with large amounts of cache and techniques (under-the-covers) to spread data and/or dynamically move it around to eliminate hot-spots, striping and distributed extents are less useful than they once were.&lt;BR /&gt;&lt;BR /&gt;3.  The default is neither.  Once again, look at the 'lvcreate' manpages.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
    <pubDate>Sat, 21 Nov 2009 15:51:17 GMT</pubDate>
    <dc:creator>James R. Ferguson</dc:creator>
    <dc:date>2009-11-21T15:51:17Z</dc:date>
    <item>
      <title>Distriputed LVM and striped LVM</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537786#M368927</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;1)How to create distriputed LVM and striped LVM?&lt;BR /&gt;&lt;BR /&gt;2)What is the purpose of those LVM?&lt;BR /&gt;&lt;BR /&gt;3)What is the default one?</description>
      <pubDate>Sat, 21 Nov 2009 11:21:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537786#M368927</guid>
      <dc:creator>senthil_kumar_1</dc:creator>
      <dc:date>2009-11-21T11:21:16Z</dc:date>
    </item>
    <item>
      <title>Re: Distriputed LVM and striped LVM</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537787#M368928</link>
      <description>Hi Senthil:&lt;BR /&gt;&lt;BR /&gt;1.  The choices are made during your logical volume creation.  See the manpages for 'lvcreate'.&lt;BR /&gt;&lt;BR /&gt;2.  The purpose is to spread I/O across as many physical disk as possible to reduce disk queue lengths on any one device and load-level I/O.  You might think of distributed extents as very large stripes.  Two drawbacks to using either is if you need to grow your logical volume you must add physical volumes to its volume group in n-units where 'n' equals the number of physical volumes over which extents are spread.  In my opinion, with modern SAN farms with large amounts of cache and techniques (under-the-covers) to spread data and/or dynamically move it around to eliminate hot-spots, striping and distributed extents are less useful than they once were.&lt;BR /&gt;&lt;BR /&gt;3.  The default is neither.  Once again, look at the 'lvcreate' manpages.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Sat, 21 Nov 2009 15:51:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537787#M368928</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2009-11-21T15:51:17Z</dc:date>
    </item>
    <item>
      <title>Re: Distriputed LVM and striped LVM</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537788#M368929</link>
      <description>1)How to create distriputed LVM and striped LVM?&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.scribd.com/doc/7782998/HPUX-System-Administrators-Guide-Logical-Volume-Management" target="_blank"&gt;http://www.scribd.com/doc/7782998/HPUX-System-Administrators-Guide-Logical-Volume-Management&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;2)What is the purpose of those LVM?&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://tldp.org/HOWTO/LVM-HOWTO/whatisvolman.html" target="_blank"&gt;http://tldp.org/HOWTO/LVM-HOWTO/whatisvolman.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;3)What is the default one?&lt;BR /&gt;&lt;BR /&gt;its depends, how you want, by default "normal" logical volume - may (1 mirror copies)&lt;BR /&gt;man lvcreate -&amp;gt; more information</description>
      <pubDate>Sat, 21 Nov 2009 16:08:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537788#M368929</guid>
      <dc:creator>Johnson Punniyalingam</dc:creator>
      <dc:date>2009-11-21T16:08:32Z</dc:date>
    </item>
    <item>
      <title>Re: Distriputed LVM and striped LVM</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537789#M368930</link>
      <description>&lt;!--!*#--&gt;Hi Senthil,&lt;BR /&gt;&lt;BR /&gt;1)How to create distributed LVM and striped LVM?&lt;BR /&gt;See Attachment&lt;BR /&gt;&lt;BR /&gt;2)What is the purpose of those LVM?&lt;BR /&gt;See Attachment (Advantages &amp;amp; Disadvantages gives you the purpose)&lt;BR /&gt;&lt;BR /&gt;3)What is the default one? &lt;BR /&gt;While creating LV you need to specify which type you are going for, else it will neither be distributed nor striped.</description>
      <pubDate>Sat, 21 Nov 2009 20:35:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537789#M368930</guid>
      <dc:creator>R.K. #</dc:creator>
      <dc:date>2009-11-21T20:35:38Z</dc:date>
    </item>
    <item>
      <title>Re: Distriputed LVM and striped LVM</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537790#M368931</link>
      <description>Si Senthil,&lt;BR /&gt;&lt;BR /&gt;Check the below links:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://networktechnologist.com/tips-hpux-lvm.html" target="_blank"&gt;http://networktechnologist.com/tips-hpux-lvm.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01919369/c01919369.pdf" target="_blank"&gt;http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01919369/c01919369.pdf&lt;/A&gt; (BSC link updated by admin)&lt;BR /&gt;&lt;BR /&gt;Rgds-Kranti</description>
      <pubDate>Sun, 22 Nov 2009 05:24:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537790#M368931</guid>
      <dc:creator>Kranti Mahmud</dc:creator>
      <dc:date>2009-11-22T05:24:12Z</dc:date>
    </item>
    <item>
      <title>Re: Distriputed LVM and striped LVM</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537791#M368932</link>
      <description>Prior to 11.31 Releases of HP-UX the Distributed Extent BAsed Striping is the implementation of RAID10 on HP_UX LVM.&lt;BR /&gt;You can keno more if you can refer to the man pages of lvcreate/lvextend.&lt;BR /&gt;this is achieved using the /etc/lvmpvg the most.&lt;BR /&gt;lvcreate -D y -s g : -D for Distributed and -s for Striped.&lt;BR /&gt;&lt;BR /&gt; The distributed allocation policy&lt;BR /&gt;                                    REQUIRES the PVG-strict allocation&lt;BR /&gt;                                    policy (-s g) to ensure that mirrors of&lt;BR /&gt;                                    distributed extents do not overlap (for&lt;BR /&gt;                                    maximum availability).&lt;BR /&gt;&lt;BR /&gt;                                    lvcreate(1M) will obtain the list of&lt;BR /&gt;                                    available physical volumes from&lt;BR /&gt;                                    /etc/lvmpvg.  See vgextend(1M) for more&lt;BR /&gt;                                    information on physical volume groups&lt;BR /&gt;                                    and /etc/lvmpvg.&lt;BR /&gt;&lt;BR /&gt;                                    When a logical volume with distributed&lt;BR /&gt;                                    extents is mirrored, the resulting&lt;BR /&gt;                                    layout is commonly referred to as&lt;BR /&gt;                                    EXTENT-BASED MIRRORED STRIPES.&lt;BR /&gt;&lt;BR /&gt;                                    Note that EXTENT-BASED MIRRORED STRIPES&lt;BR /&gt;                                    can be created without the distributed&lt;BR /&gt;                                    allocation policy by adding one extent&lt;BR /&gt;                                    at a time to the desired physical&lt;BR /&gt;                                    volumes through lvextend(1M).&lt;BR /&gt;&lt;BR /&gt;                                    The distributed allocation policy is&lt;BR /&gt;                                    incompatible with the striped scheduling&lt;BR /&gt;                                    policy (-i stripes) and the contiguous&lt;BR /&gt;                                    allocation policy (-C y).&lt;BR /&gt;&lt;BR /&gt;                                    The lvchange(1M) command can be used to&lt;BR /&gt;                                    assign the distributed allocation policy&lt;BR /&gt;                                    to an existing logical volume.&lt;BR /&gt;&lt;BR /&gt; Hewlett-Packard Company            - 4 -      HP-UX 11i Version 2: Jul 2007&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Striped LVM is the one in which the data is Striped across differnet Columns also called Diffrerent PVs.&lt;BR /&gt;lvcreate -I &lt;STRIPE_SIZE&gt; -i 3 etc :&lt;BR /&gt;&lt;BR /&gt;I Stripe Unit Size and i for number of Columns.&lt;BR /&gt;&lt;BR /&gt;Default is none: depends on what you choose your LV to be like.&lt;/STRIPE_SIZE&gt;</description>
      <pubDate>Sun, 22 Nov 2009 09:25:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537791#M368932</guid>
      <dc:creator>sujit kumar singh</dc:creator>
      <dc:date>2009-11-22T09:25:49Z</dc:date>
    </item>
    <item>
      <title>Re: Distriputed LVM and striped LVM</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537792#M368933</link>
      <description>Don't forget that block-striped volumes (as opposed to extent-striped volumes) can't be mirrored by MirrorDisk/UX.</description>
      <pubDate>Mon, 23 Nov 2009 14:00:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537792#M368933</guid>
      <dc:creator>mvpel</dc:creator>
      <dc:date>2009-11-23T14:00:20Z</dc:date>
    </item>
    <item>
      <title>Re: Distriputed LVM and striped LVM</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537793#M368934</link>
      <description>Hi Mvpel,&lt;BR /&gt;&lt;BR /&gt;Though this is an information and i have never done/come across this but .. seems that &lt;BR /&gt;that limitation is overcome perhaps in 11.31 Sep 2008 Release where a simple striped volume can also be mirrored.&lt;BR /&gt;&lt;BR /&gt;this can be reffered to page 12 of this documrnt.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01919369/c01919369.pdf" target="_blank"&gt;http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01919369/c01919369.pdf&lt;/A&gt; (BSC link updated by admin)&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;sujit</description>
      <pubDate>Mon, 23 Nov 2009 14:40:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/distriputed-lvm-and-striped-lvm/m-p/4537793#M368934</guid>
      <dc:creator>sujit kumar singh</dc:creator>
      <dc:date>2009-11-23T14:40:59Z</dc:date>
    </item>
  </channel>
</rss>

