<?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: Strange VxFS layout version in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820553#M637871</link>
    <description>That does not answer the question... :)&lt;BR /&gt;&lt;BR /&gt;You could e.g. mount an lvol and then garble the device special file. The  next open() would fail, BUT the lvol would be still mounted and accessible.&lt;BR /&gt;&lt;BR /&gt;So, does the dd work?&lt;BR /&gt;&lt;BR /&gt;Sorry for insisting on this...&lt;BR /&gt;Dietmar.</description>
    <pubDate>Tue, 08 Oct 2002 06:28:17 GMT</pubDate>
    <dc:creator>Dietmar Konermann</dc:creator>
    <dc:date>2002-10-08T06:28:17Z</dc:date>
    <item>
      <title>Strange VxFS layout version</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820550#M637868</link>
      <description>Running fstyp -v on a VxFS device (under HP-UX 11i) prints two times the error "cannot open /dev/vg00/lvol5: invalid argument" and the "version" number reported is 2^32-1. Other volumes on the system are fine and report a version 4 layout number.&lt;BR /&gt;&lt;BR /&gt;Does someone know what could give such an error?&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Tue, 08 Oct 2002 06:02:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820550#M637868</guid>
      <dc:creator>Swalens Eric</dc:creator>
      <dc:date>2002-10-08T06:02:56Z</dc:date>
    </item>
    <item>
      <title>Re: Strange VxFS layout version</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820551#M637869</link>
      <description>You should check at first if the lvol can be generally opend/read by other tools... try reading from it using dd(1) e.g. Maybe you hit a completely different, LVM-related problem...&lt;BR /&gt;&lt;BR /&gt;Regards...&lt;BR /&gt; Dietmar.</description>
      <pubDate>Tue, 08 Oct 2002 06:04:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820551#M637869</guid>
      <dc:creator>Dietmar Konermann</dc:creator>
      <dc:date>2002-10-08T06:04:20Z</dc:date>
    </item>
    <item>
      <title>Re: Strange VxFS layout version</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820552#M637870</link>
      <description>The volume is mounted on /home and seems to work fine.</description>
      <pubDate>Tue, 08 Oct 2002 06:13:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820552#M637870</guid>
      <dc:creator>Swalens Eric</dc:creator>
      <dc:date>2002-10-08T06:13:22Z</dc:date>
    </item>
    <item>
      <title>Re: Strange VxFS layout version</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820553#M637871</link>
      <description>That does not answer the question... :)&lt;BR /&gt;&lt;BR /&gt;You could e.g. mount an lvol and then garble the device special file. The  next open() would fail, BUT the lvol would be still mounted and accessible.&lt;BR /&gt;&lt;BR /&gt;So, does the dd work?&lt;BR /&gt;&lt;BR /&gt;Sorry for insisting on this...&lt;BR /&gt;Dietmar.</description>
      <pubDate>Tue, 08 Oct 2002 06:28:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820553#M637871</guid>
      <dc:creator>Dietmar Konermann</dc:creator>
      <dc:date>2002-10-08T06:28:17Z</dc:date>
    </item>
    <item>
      <title>Re: Strange VxFS layout version</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820554#M637872</link>
      <description>I see what you mean. I dump 1Mb from the beginning of the volume without any error...&lt;BR /&gt;&lt;BR /&gt;Thanks you for insisting. ;)</description>
      <pubDate>Tue, 08 Oct 2002 06:48:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820554#M637872</guid>
      <dc:creator>Swalens Eric</dc:creator>
      <dc:date>2002-10-08T06:48:08Z</dc:date>
    </item>
    <item>
      <title>Re: Strange VxFS layout version</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820555#M637873</link>
      <description>Hi!&lt;BR /&gt;&lt;BR /&gt;Sorry, I missed some important info in your initial post... you actuall _get_ some results from fstyp, but only bogus ones.&lt;BR /&gt;&lt;BR /&gt;This really looks like the problem reported as JAGad24643 which is fixed with 11.22. It usually happens after extending or upgrading the FS.&lt;BR /&gt;&lt;BR /&gt;At this point in time no official 11.11 patch is avialable. You should contact your local RC if needed.&lt;BR /&gt;&lt;BR /&gt;Regards...&lt;BR /&gt; Dietmar.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Oct 2002 20:48:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820555#M637873</guid>
      <dc:creator>Dietmar Konermann</dc:creator>
      <dc:date>2002-10-08T20:48:30Z</dc:date>
    </item>
    <item>
      <title>Re: Strange VxFS layout version</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820556#M637874</link>
      <description>Thank you very much for your help.&lt;BR /&gt;&lt;BR /&gt;Where can I find more information about JAGad24643? Is there a description of the bug and its consequences available online?&lt;BR /&gt;&lt;BR /&gt;Eric</description>
      <pubDate>Wed, 09 Oct 2002 06:06:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820556#M637874</guid>
      <dc:creator>Swalens Eric</dc:creator>
      <dc:date>2002-10-09T06:06:43Z</dc:date>
    </item>
    <item>
      <title>Re: Strange VxFS layout version</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820557#M637875</link>
      <description>Hi!&lt;BR /&gt;&lt;BR /&gt;Sorry, there is currently only internal documentation about this. Root cause is a missing buffer initialization before usage.&lt;BR /&gt;&lt;BR /&gt;Hint: the latest fstyp patch for 11.00 should include the fix. So you could take PHCO_27567 and fetch the /sbin/fstyp binary from there. Works fine on 11.11 also... of course this would only be an unsupported workaround until an 11.11 patch is released.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards...&lt;BR /&gt; Dietmar.</description>
      <pubDate>Wed, 09 Oct 2002 07:19:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820557#M637875</guid>
      <dc:creator>Dietmar Konermann</dc:creator>
      <dc:date>2002-10-09T07:19:45Z</dc:date>
    </item>
    <item>
      <title>Re: Strange VxFS layout version</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820558#M637876</link>
      <description>OK.&lt;BR /&gt;Thanks for your help.&lt;BR /&gt;&lt;BR /&gt;Eric</description>
      <pubDate>Wed, 09 Oct 2002 09:24:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/strange-vxfs-layout-version/m-p/2820558#M637876</guid>
      <dc:creator>Swalens Eric</dc:creator>
      <dc:date>2002-10-09T09:24:47Z</dc:date>
    </item>
  </channel>
</rss>

