<?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 vdump error in Operating System - Tru64 Unix</title>
    <link>https://community.hpe.com/t5/operating-system-tru64-unix/vdump-error/m-p/4859070#M10754</link>
    <description>Hi folks,&lt;BR /&gt;&lt;BR /&gt;I'm getting a very unusual error when I am trying to run a vdump on the /usr filesystem of a DS15. &lt;BR /&gt;&lt;BR /&gt;vdump -0 -f /u10/usr.dmp /usr&lt;BR /&gt;path     : /usr&lt;BR /&gt;dev/fset : usr_domain#usr&lt;BR /&gt;type     : advfs&lt;BR /&gt;advfs id : 0x40083948.0004dae0.1&lt;BR /&gt;vdump: Date of last level 0 dump: the start of the epoch&lt;BR /&gt;vdump: Dumping directories&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;************* PROGRAM ABORT **************&lt;BR /&gt;&lt;BR /&gt;vdump: Not enough memory to generate link table.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;This happens to be an administration system, so I'm betting the kernel isn't quite tuned properly.  Has anyone run across this and know the answer?&lt;BR /&gt;&lt;BR /&gt;The system is running 5.1B PK4.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;--Blake Roberts</description>
    <pubDate>Wed, 01 Sep 2004 11:18:50 GMT</pubDate>
    <dc:creator>Blake Roberts</dc:creator>
    <dc:date>2004-09-01T11:18:50Z</dc:date>
    <item>
      <title>vdump error</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/vdump-error/m-p/4859070#M10754</link>
      <description>Hi folks,&lt;BR /&gt;&lt;BR /&gt;I'm getting a very unusual error when I am trying to run a vdump on the /usr filesystem of a DS15. &lt;BR /&gt;&lt;BR /&gt;vdump -0 -f /u10/usr.dmp /usr&lt;BR /&gt;path     : /usr&lt;BR /&gt;dev/fset : usr_domain#usr&lt;BR /&gt;type     : advfs&lt;BR /&gt;advfs id : 0x40083948.0004dae0.1&lt;BR /&gt;vdump: Date of last level 0 dump: the start of the epoch&lt;BR /&gt;vdump: Dumping directories&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;************* PROGRAM ABORT **************&lt;BR /&gt;&lt;BR /&gt;vdump: Not enough memory to generate link table.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;This happens to be an administration system, so I'm betting the kernel isn't quite tuned properly.  Has anyone run across this and know the answer?&lt;BR /&gt;&lt;BR /&gt;The system is running 5.1B PK4.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;--Blake Roberts</description>
      <pubDate>Wed, 01 Sep 2004 11:18:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/vdump-error/m-p/4859070#M10754</guid>
      <dc:creator>Blake Roberts</dc:creator>
      <dc:date>2004-09-01T11:18:50Z</dc:date>
    </item>
    <item>
      <title>Re: vdump error</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/vdump-error/m-p/4859071#M10755</link>
      <description>Did you check the swap space available, memory available. Please post the swapon -a and vmstat -P outputs&lt;BR /&gt;&lt;BR /&gt;thanks</description>
      <pubDate>Wed, 01 Sep 2004 12:42:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/vdump-error/m-p/4859071#M10755</guid>
      <dc:creator>Mohamed  K Ahmed</dc:creator>
      <dc:date>2004-09-01T12:42:01Z</dc:date>
    </item>
    <item>
      <title>Re: vdump error</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/vdump-error/m-p/4859072#M10756</link>
      <description>&lt;BR /&gt;&amp;gt; swapon -s&lt;BR /&gt;Swap partition /dev/vol/rootdg/swapvol (default swap):&lt;BR /&gt;    Allocated space:       512000 pages (3.91GB)&lt;BR /&gt;    In-use space:               1 pages (  0%)&lt;BR /&gt;    Free space:            511999 pages ( 99%)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Total swap allocation:&lt;BR /&gt;    Allocated space:       512000 pages (3.91GB)&lt;BR /&gt;    Reserved space:         15015 pages (  2%)&lt;BR /&gt;    In-use space:               1 pages (  0%)&lt;BR /&gt;    Available space:       496985 pages ( 97%)&lt;BR /&gt;&lt;BR /&gt;&amp;gt; vmstat -P&lt;BR /&gt;&lt;BR /&gt;Total Physical Memory =  1024.00 M&lt;BR /&gt;                      =   131072 pages&lt;BR /&gt;&lt;BR /&gt;Physical Memory Clusters:&lt;BR /&gt;&lt;BR /&gt;start_pfn     end_pfn        type  size_pages / size_bytes&lt;BR /&gt;         0         350         pal         350 /    2.73M&lt;BR /&gt;       350      131063          os      130713 / 1021.20M&lt;BR /&gt;    131063      131072         pal           9 /   72.00k&lt;BR /&gt;&lt;BR /&gt;Physical Memory Use:&lt;BR /&gt;&lt;BR /&gt; start_pfn     end_pfn        type  size_pages / size_bytes&lt;BR /&gt;       350         545    scavenge         195 /    1.52M&lt;BR /&gt;       545        1429        text         884 /    6.91M&lt;BR /&gt;      1429        1597        data         168 /    1.31M&lt;BR /&gt;      1597        1831         bss         234 /    1.83M&lt;BR /&gt;      1831        2049      kdebug         218 /    1.70M&lt;BR /&gt;      2049        2056     cfgmgmt           7 /   56.00k&lt;BR /&gt;      2056        2057       locks           1 /    8.00k&lt;BR /&gt;      2057        2071        pmap          14 /  112.00k&lt;BR /&gt;      2071        3028   unixtable         957 /    7.48M&lt;BR /&gt;      3028        3052        logs          24 /  192.00k&lt;BR /&gt;      3052        6047    vmtables        2995 /   23.40M&lt;BR /&gt;      6047      131063     managed      125016 /  976.69M&lt;BR /&gt;                             ============================&lt;BR /&gt;         Total Physical Memory Use:     130713 / 1021.20M&lt;BR /&gt;&lt;BR /&gt;Managed Pages Break Down:&lt;BR /&gt;&lt;BR /&gt;       free pages = 20014&lt;BR /&gt;     active pages = 484&lt;BR /&gt;   inactive pages = 10461&lt;BR /&gt;      wired pages = 17333&lt;BR /&gt;        ubc pages = 76918&lt;BR /&gt;        ==================&lt;BR /&gt;            Total = 125210&lt;BR /&gt;&lt;BR /&gt;WIRED Pages Break Down:&lt;BR /&gt;&lt;BR /&gt;   vm wired pages = 2814&lt;BR /&gt;  ubc wired pages = 0&lt;BR /&gt;  meta data pages = 3869&lt;BR /&gt;     malloc pages = 7374&lt;BR /&gt;     contig pages = 2356&lt;BR /&gt;    user ptepages = 782&lt;BR /&gt;  kernel ptepages = 130&lt;BR /&gt;    free ptepages = 8&lt;BR /&gt;        ==================&lt;BR /&gt;            Total = 17333&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Sep 2004 12:46:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/vdump-error/m-p/4859072#M10756</guid>
      <dc:creator>Blake Roberts</dc:creator>
      <dc:date>2004-09-01T12:46:42Z</dc:date>
    </item>
    <item>
      <title>Re: vdump error</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/vdump-error/m-p/4859073#M10757</link>
      <description>My partner answered the question.  He set all of the ulimits to "unlimited" and it worked.  AS I suspected, since this is an admin box, it hasn't been kernel tuned properly.&lt;BR /&gt;&lt;BR /&gt;Ulimits... we don't need no stinkin' ulimits!&lt;BR /&gt;&lt;BR /&gt;Thanks for the help,&lt;BR /&gt;--Blake&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Sep 2004 13:46:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/vdump-error/m-p/4859073#M10757</guid>
      <dc:creator>Blake Roberts</dc:creator>
      <dc:date>2004-09-01T13:46:50Z</dc:date>
    </item>
    <item>
      <title>Re: vdump error</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/vdump-error/m-p/4859074#M10758</link>
      <description>See note above.</description>
      <pubDate>Wed, 01 Sep 2004 13:48:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/vdump-error/m-p/4859074#M10758</guid>
      <dc:creator>Blake Roberts</dc:creator>
      <dc:date>2004-09-01T13:48:00Z</dc:date>
    </item>
  </channel>
</rss>

