<?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: LVM volume name in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593874#M623583</link>
    <description>What does the author mean by "pretty long names" ?  &lt;BR /&gt;"BeautifulDreamer001" ?  :-)&lt;BR /&gt;&lt;BR /&gt;lvol2 is long enough for me.  But, it's probably not all that pretty.  :-)&lt;BR /&gt;</description>
    <pubDate>Mon, 01 Aug 2005 11:12:28 GMT</pubDate>
    <dc:creator>TwoProc</dc:creator>
    <dc:date>2005-08-01T11:12:28Z</dc:date>
    <item>
      <title>LVM volume name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593866#M623575</link>
      <description>Are there any constraints on the length of the volume name? I guess, the constraints are the same as in the case of the filename. Am I wrong?&lt;BR /&gt;&lt;BR /&gt;M. Brachtl</description>
      <pubDate>Mon, 01 Aug 2005 09:16:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593866#M623575</guid>
      <dc:creator>Martin Brachtl</dc:creator>
      <dc:date>2005-08-01T09:16:26Z</dc:date>
    </item>
    <item>
      <title>Re: LVM volume name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593867#M623576</link>
      <description>That's all the man page says:&lt;BR /&gt;&lt;BR /&gt;"where lv_name is a simple file name, not a path name"&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Mon, 01 Aug 2005 09:23:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593867#M623576</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2005-08-01T09:23:49Z</dc:date>
    </item>
    <item>
      <title>Re: LVM volume name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593868#M623577</link>
      <description>well, I read that, but this is not "a proof" that there are no other constraints.</description>
      <pubDate>Mon, 01 Aug 2005 09:28:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593868#M623577</guid>
      <dc:creator>Martin Brachtl</dc:creator>
      <dc:date>2005-08-01T09:28:26Z</dc:date>
    </item>
    <item>
      <title>Re: LVM volume name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593869#M623578</link>
      <description>I would keep not get crazy with the naming.  Remember if something goes wrong your gonna have to type these puppies.</description>
      <pubDate>Mon, 01 Aug 2005 09:30:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593869#M623578</guid>
      <dc:creator>generic_1</dc:creator>
      <dc:date>2005-08-01T09:30:47Z</dc:date>
    </item>
    <item>
      <title>Re: LVM volume name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593870#M623579</link>
      <description>Keep it somewhat short and it will keep the `bdf` output on 1 line.&lt;BR /&gt;&lt;BR /&gt;Get longer vg_ &amp;amp; lv_ names and the `bdf` display has too use multiple lines.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Aug 2005 09:32:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593870#M623579</guid>
      <dc:creator>Rick Garland</dc:creator>
      <dc:date>2005-08-01T09:32:58Z</dc:date>
    </item>
    <item>
      <title>Re: LVM volume name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593871#M623580</link>
      <description>I am asking because the author of application suggested pretty long names. Shall I say to him, silly long names, but it will work, or, will not.&lt;BR /&gt;&lt;BR /&gt;M. Br.</description>
      <pubDate>Mon, 01 Aug 2005 09:44:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593871#M623580</guid>
      <dc:creator>Martin Brachtl</dc:creator>
      <dc:date>2005-08-01T09:44:12Z</dc:date>
    </item>
    <item>
      <title>Re: LVM volume name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593872#M623581</link>
      <description>It will work, but there is a point where readability clashes with useability, especially if you are the system administrator.&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Aug 2005 11:02:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593872#M623581</guid>
      <dc:creator>Kent Ostby</dc:creator>
      <dc:date>2005-08-01T11:02:25Z</dc:date>
    </item>
    <item>
      <title>Re: LVM volume name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593873#M623582</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I wouldn't use very long names, they are not pratical for administration, some tools like Glance, MeasureWare, OVO will truncate those names.&lt;BR /&gt;&lt;BR /&gt;Enjoy :)</description>
      <pubDate>Mon, 01 Aug 2005 11:09:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593873#M623582</guid>
      <dc:creator>Pedro Cirne</dc:creator>
      <dc:date>2005-08-01T11:09:35Z</dc:date>
    </item>
    <item>
      <title>Re: LVM volume name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593874#M623583</link>
      <description>What does the author mean by "pretty long names" ?  &lt;BR /&gt;"BeautifulDreamer001" ?  :-)&lt;BR /&gt;&lt;BR /&gt;lvol2 is long enough for me.  But, it's probably not all that pretty.  :-)&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Aug 2005 11:12:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593874#M623583</guid>
      <dc:creator>TwoProc</dc:creator>
      <dc:date>2005-08-01T11:12:28Z</dc:date>
    </item>
    <item>
      <title>Re: LVM volume name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593875#M623584</link>
      <description>The long names will work.&lt;BR /&gt;&lt;BR /&gt;Do keep in mind the balance act between readability and useability</description>
      <pubDate>Mon, 01 Aug 2005 11:36:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593875#M623584</guid>
      <dc:creator>Rick Garland</dc:creator>
      <dc:date>2005-08-01T11:36:40Z</dc:date>
    </item>
    <item>
      <title>Re: LVM volume name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593876#M623585</link>
      <description>Tell the developer that the system administration policies do not allow for fancy names. After all, where will those volume groups be used? As parameters and/or answers to questions in the application? Or just some names in a config file? VG's are sysadmin symbols. Long VG names will create a *LOT* of sysadmin pain in the future as apps (like Glance and OV) and tools like bdf try to work around the long names. It won't be pretty...</description>
      <pubDate>Mon, 01 Aug 2005 17:32:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593876#M623585</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-08-01T17:32:14Z</dc:date>
    </item>
    <item>
      <title>Re: LVM volume name</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593877#M623586</link>
      <description>"Pretty long" is something like this:&lt;BR /&gt;&lt;BR /&gt;/dev/vgxx/cust_scoring1_db12_arch_log_w_1&lt;BR /&gt;&lt;BR /&gt;I would not choose anything like that, because of all reasons you mentioned. And I was not sure, if this is also technically possible. It seems, it is.&lt;BR /&gt;&lt;BR /&gt;BTW thank you all for the responses.&lt;BR /&gt;&lt;BR /&gt;MBr.</description>
      <pubDate>Tue, 02 Aug 2005 02:12:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-volume-name/m-p/3593877#M623586</guid>
      <dc:creator>Martin Brachtl</dc:creator>
      <dc:date>2005-08-02T02:12:55Z</dc:date>
    </item>
  </channel>
</rss>

