<?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: fbackup to wrong path-root full in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079843#M731152</link>
    <description>Yes i believe.&lt;BR /&gt;What is the index file name?&lt;BR /&gt;I did not see any big lates file created which can cause the root full.</description>
    <pubDate>Fri, 16 Nov 2007 02:10:44 GMT</pubDate>
    <dc:creator>Fauziah Mahdan</dc:creator>
    <dc:date>2007-11-16T02:10:44Z</dc:date>
    <item>
      <title>fbackup to wrong path-root full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079841#M731150</link>
      <description>Hi all,&lt;BR /&gt;I run fbackup just now but the path was wrong and it goes to root directory and make my root full.&lt;BR /&gt;What type of files I can remove from root directory which is generated due to fbackup command?&lt;BR /&gt;</description>
      <pubDate>Fri, 16 Nov 2007 01:31:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079841#M731150</guid>
      <dc:creator>Fauziah Mahdan</dc:creator>
      <dc:date>2007-11-16T01:31:52Z</dc:date>
    </item>
    <item>
      <title>Re: fbackup to wrong path-root full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079842#M731151</link>
      <description>you mean to say that you created backup it self on the root filesystem instead of taking on tape ??&lt;BR /&gt;&lt;BR /&gt;If that so then delte index and backup files then initiate the backup once again using the old graph file on tape or a new path.. If you are not sure then you can keep a copy of the current things in some other directory. Once you are sure that it is not required then those files can be deleted.</description>
      <pubDate>Fri, 16 Nov 2007 01:41:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079842#M731151</guid>
      <dc:creator>Mridul Shrivastava</dc:creator>
      <dc:date>2007-11-16T01:41:25Z</dc:date>
    </item>
    <item>
      <title>Re: fbackup to wrong path-root full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079843#M731152</link>
      <description>Yes i believe.&lt;BR /&gt;What is the index file name?&lt;BR /&gt;I did not see any big lates file created which can cause the root full.</description>
      <pubDate>Fri, 16 Nov 2007 02:10:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079843#M731152</guid>
      <dc:creator>Fauziah Mahdan</dc:creator>
      <dc:date>2007-11-16T02:10:44Z</dc:date>
    </item>
    <item>
      <title>Re: fbackup to wrong path-root full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079844#M731153</link>
      <description>Index file is the file which contains all info about backed up files. During running fbackup you should give index file name with -I option so that you can view it later to trace backed up items.&lt;BR /&gt;&lt;BR /&gt;-=ShRi=-</description>
      <pubDate>Fri, 16 Nov 2007 02:16:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079844#M731153</guid>
      <dc:creator>Shrikant Lavhate</dc:creator>
      <dc:date>2007-11-16T02:16:16Z</dc:date>
    </item>
    <item>
      <title>Re: fbackup to wrong path-root full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079845#M731154</link>
      <description>Fauziah,&lt;BR /&gt;&lt;BR /&gt; Check your tape device, see got any big files written to device&lt;BR /&gt;&lt;BR /&gt;#ll /dev/rmt/*&lt;BR /&gt;&lt;BR /&gt;WK</description>
      <pubDate>Fri, 16 Nov 2007 03:03:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079845#M731154</guid>
      <dc:creator>whiteknight</dc:creator>
      <dc:date>2007-11-16T03:03:55Z</dc:date>
    </item>
    <item>
      <title>Re: fbackup to wrong path-root full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079846#M731155</link>
      <description>OK I think I know but need some clarification.&lt;BR /&gt;I was typing command fbackup -vf /dev/rmt/2m -i /&lt;BR /&gt;&lt;BR /&gt;The right command should in /dev/rmt/0m&lt;BR /&gt;&lt;BR /&gt;So when I check /dev/rmt&lt;BR /&gt;I found filename 2m&lt;BR /&gt;SO temp I move this 2m and my root decrease to 27% and rerun another backup into the right path /dev/rmt/0m (dds4tape).&lt;BR /&gt;&lt;BR /&gt;Pls comment&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 16 Nov 2007 03:45:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079846#M731155</guid>
      <dc:creator>Fauziah Mahdan</dc:creator>
      <dc:date>2007-11-16T03:45:14Z</dc:date>
    </item>
    <item>
      <title>Re: fbackup to wrong path-root full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079847#M731156</link>
      <description>yes, you got it right....  that was the archive file which contains all the backed up files...&lt;BR /&gt;&lt;BR /&gt;Now you can safely re-run the fbackup using the correct device file name... for more details and options please refer man pages.</description>
      <pubDate>Fri, 16 Nov 2007 17:35:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079847#M731156</guid>
      <dc:creator>Mridul Shrivastava</dc:creator>
      <dc:date>2007-11-16T17:35:42Z</dc:date>
    </item>
    <item>
      <title>Re: fbackup to wrong path-root full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079848#M731157</link>
      <description>All of the backup programs such as fbackup or tar or cpio will not tell you if the output device does not exist. Instead, if you make a spelling error, in your case, 2m rather than 0m, then the programs will create an ordinary file and put all of the data in that file. Remove the 2m file as it was a mistake. Always verify that the output file, the -f option, is the correct tape drive. The lssf command is useful:&lt;BR /&gt;  &lt;BR /&gt;lssf /dev/rmt/2m&lt;BR /&gt;lssf /dev/rmt/0m&lt;BR /&gt; &lt;BR /&gt;The man page for lssf is useful.</description>
      <pubDate>Sun, 18 Nov 2007 19:20:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079848#M731157</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2007-11-18T19:20:24Z</dc:date>
    </item>
    <item>
      <title>Re: fbackup to wrong path-root full</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079849#M731158</link>
      <description>Thanks all&lt;BR /&gt;:-)&lt;BR /&gt;</description>
      <pubDate>Tue, 27 Nov 2007 20:40:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fbackup-to-wrong-path-root-full/m-p/5079849#M731158</guid>
      <dc:creator>Fauziah Mahdan</dc:creator>
      <dc:date>2007-11-27T20:40:51Z</dc:date>
    </item>
  </channel>
</rss>

