<?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: lvmtab corrupted in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lvmtab-corrupted/m-p/3458761#M624422</link>
    <description>Hu Kuzo,&lt;BR /&gt;&lt;BR /&gt;The /etc/lvmtab file is binary. Because the strings(1) command&lt;BR /&gt;is looking for ASCII strings in a binary file, ocassionaly&lt;BR /&gt;strange characters will appear.&lt;BR /&gt;&lt;BR /&gt;/dev/vg00&lt;BR /&gt;MAb#-&lt;BR /&gt;/dev/dsk/c2t0d0&lt;BR /&gt;/dev/dsk/c2t1d0&lt;BR /&gt;&lt;BR /&gt;You have nothing to worry about when you see this display.&lt;BR /&gt;strings on /etc/lvmtab is not a command that is supposed to&lt;BR /&gt;tell you about the vg configurations on your system. You are&lt;BR /&gt;supposed to use vgdisplay on the individual vg's.&lt;BR /&gt;&lt;BR /&gt;The strings command is just a way to "cheat" and see info on all&lt;BR /&gt;the vg's at once. It leverages how strings pulls ascii characters&lt;BR /&gt;out of unformated files and so if any strings of ascii characters&lt;BR /&gt;exist other than the vg info then they will be displayed.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Robert-Jan</description>
    <pubDate>Sun, 09 Jan 2005 06:07:01 GMT</pubDate>
    <dc:creator>Robert-Jan Goossens</dc:creator>
    <dc:date>2005-01-09T06:07:01Z</dc:date>
    <item>
      <title>lvmtab corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvmtab-corrupted/m-p/3458760#M624421</link>
      <description>Dear,&lt;BR /&gt;The output of the command strings /etc/lvmtab &lt;BR /&gt;/dev/vg00&lt;BR /&gt;MAb#-&lt;BR /&gt;/dev/dsk/c2t0d0&lt;BR /&gt;/dev/dsk/c2t1d0&lt;BR /&gt;I don't understand what is MAb#,&lt;BR /&gt;On this node I just imported vg and create and remove it&lt;BR /&gt;I need your help&lt;BR /&gt;KSF&lt;BR /&gt;</description>
      <pubDate>Sun, 09 Jan 2005 05:53:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvmtab-corrupted/m-p/3458760#M624421</guid>
      <dc:creator>sassou</dc:creator>
      <dc:date>2005-01-09T05:53:30Z</dc:date>
    </item>
    <item>
      <title>Re: lvmtab corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvmtab-corrupted/m-p/3458761#M624422</link>
      <description>Hu Kuzo,&lt;BR /&gt;&lt;BR /&gt;The /etc/lvmtab file is binary. Because the strings(1) command&lt;BR /&gt;is looking for ASCII strings in a binary file, ocassionaly&lt;BR /&gt;strange characters will appear.&lt;BR /&gt;&lt;BR /&gt;/dev/vg00&lt;BR /&gt;MAb#-&lt;BR /&gt;/dev/dsk/c2t0d0&lt;BR /&gt;/dev/dsk/c2t1d0&lt;BR /&gt;&lt;BR /&gt;You have nothing to worry about when you see this display.&lt;BR /&gt;strings on /etc/lvmtab is not a command that is supposed to&lt;BR /&gt;tell you about the vg configurations on your system. You are&lt;BR /&gt;supposed to use vgdisplay on the individual vg's.&lt;BR /&gt;&lt;BR /&gt;The strings command is just a way to "cheat" and see info on all&lt;BR /&gt;the vg's at once. It leverages how strings pulls ascii characters&lt;BR /&gt;out of unformated files and so if any strings of ascii characters&lt;BR /&gt;exist other than the vg info then they will be displayed.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Robert-Jan</description>
      <pubDate>Sun, 09 Jan 2005 06:07:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvmtab-corrupted/m-p/3458761#M624422</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2005-01-09T06:07:01Z</dc:date>
    </item>
    <item>
      <title>Re: lvmtab corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvmtab-corrupted/m-p/3458762#M624423</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;if you want to correct it and to have a "look good" lvmtab you can save /etc/lvmtab in other directory and recreate it:&lt;BR /&gt;&lt;BR /&gt;# mv /etc/lvmtab /tmp/lvmtab.old&lt;BR /&gt;# vgscan -v -a&lt;BR /&gt;&lt;BR /&gt;Stf ;-)</description>
      <pubDate>Sun, 09 Jan 2005 06:52:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvmtab-corrupted/m-p/3458762#M624423</guid>
      <dc:creator>Stf</dc:creator>
      <dc:date>2005-01-09T06:52:39Z</dc:date>
    </item>
    <item>
      <title>Re: lvmtab corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvmtab-corrupted/m-p/3458763#M624424</link>
      <description>Recreating lvmtab will likely produce the same result. As mentioned, lvmtab is NOT an ASCII file and contains a bunch of binary numbers and character strings. Using the strings command is a hack to see the device files (which are ASCII strings). But some of the binary numbers may look like ASCII strings but are meaningless. The numbers are only meaningful to the LVM code.</description>
      <pubDate>Sun, 09 Jan 2005 20:07:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvmtab-corrupted/m-p/3458763#M624424</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-01-09T20:07:16Z</dc:date>
    </item>
    <item>
      <title>Re: lvmtab corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvmtab-corrupted/m-p/3458764#M624425</link>
      <description>As already explained /etc/lvmtab ins't a ASCII file and doing strings is a hack. When doing it I always use 'strings /etc/lvmtab | grep dev'.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Trond</description>
      <pubDate>Mon, 10 Jan 2005 03:10:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvmtab-corrupted/m-p/3458764#M624425</guid>
      <dc:creator>Trond Haugen</dc:creator>
      <dc:date>2005-01-10T03:10:08Z</dc:date>
    </item>
    <item>
      <title>Re: lvmtab corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvmtab-corrupted/m-p/3458765#M624426</link>
      <description>Do not worry. It is OK. lvmtab alway contains unfamily character. (binary format).&lt;BR /&gt;But i recommend you "export -p -m" all vgs (expecially vg00) to back it up. when problem occur vgimport again.&lt;BR /&gt;tienna</description>
      <pubDate>Sun, 16 Jan 2005 04:50:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvmtab-corrupted/m-p/3458765#M624426</guid>
      <dc:creator>Nguyen Anh Tien</dc:creator>
      <dc:date>2005-01-16T04:50:17Z</dc:date>
    </item>
  </channel>
</rss>

