<?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: make_sys_image command failed in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/make-sys-image-command-failed/m-p/5055099#M506445</link>
    <description>Had to re-create file system to enable largefiles.  &lt;BR /&gt;It works!&lt;BR /&gt;&lt;BR /&gt;Thanks for all your help.</description>
    <pubDate>Tue, 10 Jul 2007 15:02:51 GMT</pubDate>
    <dc:creator>valcor</dc:creator>
    <dc:date>2007-07-10T15:02:51Z</dc:date>
    <item>
      <title>make_sys_image command failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/make-sys-image-command-failed/m-p/5055095#M506441</link>
      <description>Hello,&lt;BR /&gt;I have an itanium server running HP-UX v11.23&lt;BR /&gt;Is there an option in ignite during the make_net_recovery to archive the contents of a client via tar to another directory?  I got to the part where it says:&lt;BR /&gt;&lt;BR /&gt;  *Archiving contents of client via tar to&lt;BR /&gt;   /var/opt/ignite/recovery/arch_mnt/2007-06-26,15;35&lt;BR /&gt;gzip: stdout: File too large&lt;BR /&gt;ERROR: the gzip command failed (exit status 1)&lt;BR /&gt;ERROR: The make_sys_image command failed. The system recovery archive will not be created.&lt;BR /&gt;&lt;BR /&gt;Instead of /var/opt/ignite/recovery/arch_mnt, can I point it to another directory, ie. /temp/recovery/arch_mnt?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.</description>
      <pubDate>Tue, 26 Jun 2007 20:09:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/make-sys-image-command-failed/m-p/5055095#M506441</guid>
      <dc:creator>valcor</dc:creator>
      <dc:date>2007-06-26T20:09:05Z</dc:date>
    </item>
    <item>
      <title>Re: make_sys_image command failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/make-sys-image-command-failed/m-p/5055096#M506442</link>
      <description>Hi Valcor,&lt;BR /&gt;&lt;BR /&gt;1] Ignite-UX creates a symbolic link between directories named after the clientâ  s name and its MAC address. For example, if you had a system with a client name of "longs_peak" and a MAC address of "0x00306E4C9B54", the directories /var/opt/ignite/clients/0x00306E4C9B54 and /var/opt/ignite/clients/longs_peak would be symbolically linked. &lt;BR /&gt;&lt;BR /&gt;2] You can specify what additional volume groups, directories, and files you want included, and what directories and files you want excluded. This is done using simple syntax in the client-specific content file, /var/opt/ignite/clients/client/recovery/archive_content, or by using command line options. You are not restricted to one or two volume groups. You can create a complete multi-volume group recovery image.&lt;BR /&gt;&lt;BR /&gt;3] You can use the user interface (launched with the -i option to make_[tape|net]_recovery) to find out which volume groups and/or disks will be untouched, which will be partially restored, and which will be restored in full if the recovery image is used, based on the specifications in the mnr_essentials file and the archive_content file. &lt;BR /&gt;&lt;BR /&gt;You can also use the user interface to edit the archive_content file and dynamically see the changes in the volume groups and disks that are affected. &lt;BR /&gt;&lt;BR /&gt;Refer followinf document for details:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B2355-91049/ch11s02.html" target="_blank"&gt;http://docs.hp.com/en/B2355-91049/ch11s02.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks &amp;amp; Regards&lt;BR /&gt;Reshma</description>
      <pubDate>Tue, 26 Jun 2007 22:35:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/make-sys-image-command-failed/m-p/5055096#M506442</guid>
      <dc:creator>Reshma Malusare</dc:creator>
      <dc:date>2007-06-26T22:35:08Z</dc:date>
    </item>
    <item>
      <title>Re: make_sys_image command failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/make-sys-image-command-failed/m-p/5055097#M506443</link>
      <description>You don't have largefiles enabled on the filesystem&lt;BR /&gt;&lt;BR /&gt;fsadm -F vxfs -o largefiles &lt;MOUNTPOINT&gt;&lt;/MOUNTPOINT&gt;</description>
      <pubDate>Wed, 27 Jun 2007 23:37:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/make-sys-image-command-failed/m-p/5055097#M506443</guid>
      <dc:creator>Radovan Rovny</dc:creator>
      <dc:date>2007-06-27T23:37:45Z</dc:date>
    </item>
    <item>
      <title>Re: make_sys_image command failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/make-sys-image-command-failed/m-p/5055098#M506444</link>
      <description>Thanks for all your replies.&lt;BR /&gt;&lt;BR /&gt;I did check my file system setting and found that it was not largefile enabled.&lt;BR /&gt;&lt;BR /&gt;Will make necessary changes.&lt;BR /&gt;&lt;BR /&gt;Thanks again.</description>
      <pubDate>Thu, 28 Jun 2007 09:41:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/make-sys-image-command-failed/m-p/5055098#M506444</guid>
      <dc:creator>valcor</dc:creator>
      <dc:date>2007-06-28T09:41:41Z</dc:date>
    </item>
    <item>
      <title>Re: make_sys_image command failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/make-sys-image-command-failed/m-p/5055099#M506445</link>
      <description>Had to re-create file system to enable largefiles.  &lt;BR /&gt;It works!&lt;BR /&gt;&lt;BR /&gt;Thanks for all your help.</description>
      <pubDate>Tue, 10 Jul 2007 15:02:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/make-sys-image-command-failed/m-p/5055099#M506445</guid>
      <dc:creator>valcor</dc:creator>
      <dc:date>2007-07-10T15:02:51Z</dc:date>
    </item>
  </channel>
</rss>

