<?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: Fragmentation of disk drive in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900962#M80211</link>
    <description>There are free utilities such as DFU and reporting programs that come with HP DFO.&lt;BR /&gt;Executive software also do a free fragmentation reporting utility - see&lt;BR /&gt;&lt;A href="http://www.executive.com/freeware/freeware.asp" target="_blank"&gt;http://www.executive.com/freeware/freeware.asp&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;You can see if file fragmentation is having an affect by looking at window turns and split I/O rate in the MONITOR utility.</description>
    <pubDate>Mon, 20 Nov 2006 05:12:37 GMT</pubDate>
    <dc:creator>Ian Miller.</dc:creator>
    <dc:date>2006-11-20T05:12:37Z</dc:date>
    <item>
      <title>Fragmentation of disk drive</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900961#M80210</link>
      <description>How can i check the fragmentation of any disk drive,and is it possible to defrag the volume  without dismounting the device.</description>
      <pubDate>Mon, 20 Nov 2006 05:00:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900961#M80210</guid>
      <dc:creator>Mrityunjoy Kundu</dc:creator>
      <dc:date>2006-11-20T05:00:12Z</dc:date>
    </item>
    <item>
      <title>Re: Fragmentation of disk drive</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900962#M80211</link>
      <description>There are free utilities such as DFU and reporting programs that come with HP DFO.&lt;BR /&gt;Executive software also do a free fragmentation reporting utility - see&lt;BR /&gt;&lt;A href="http://www.executive.com/freeware/freeware.asp" target="_blank"&gt;http://www.executive.com/freeware/freeware.asp&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;You can see if file fragmentation is having an affect by looking at window turns and split I/O rate in the MONITOR utility.</description>
      <pubDate>Mon, 20 Nov 2006 05:12:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900962#M80211</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2006-11-20T05:12:37Z</dc:date>
    </item>
    <item>
      <title>Re: Fragmentation of disk drive</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900963#M80212</link>
      <description>The DFU utility (from HP, found on the freeware archives) can create reports on disk usage, containing fragmentation indexes for the files and for the free space.&lt;BR /&gt;It also allows for the defragmentation of individual files (more like COPY/CONTIG does).&lt;BR /&gt;To defragment complete disks under load you may use the HP product 'Disk File Optimizer',but that costs money.&lt;BR /&gt;&lt;BR /&gt;regards Kalle</description>
      <pubDate>Mon, 20 Nov 2006 05:15:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900963#M80212</guid>
      <dc:creator>Karl Rohwedder</dc:creator>
      <dc:date>2006-11-20T05:15:00Z</dc:date>
    </item>
    <item>
      <title>Re: Fragmentation of disk drive</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900964#M80213</link>
      <description>And note that open files are not defragmented. So, close as much as possible. Restart long running processes that are generating big log files as much as possible because they might lock small segments scattered all over the disk thus preventing free space consolidation.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Mon, 20 Nov 2006 06:25:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900964#M80213</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2006-11-20T06:25:27Z</dc:date>
    </item>
    <item>
      <title>Re: Fragmentation of disk drive</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900965#M80214</link>
      <description>Almost all the defragmenters have a free tool that lets you check fragmentation.&lt;BR /&gt;&lt;BR /&gt;This includes DFO.&lt;BR /&gt;&lt;BR /&gt;Not all fragmentation is bad, since it uses the last freed block to use a block.  Thus, some mixture of free space, contrary to popular wisdom, will improve performance.&lt;BR /&gt;&lt;BR /&gt;Larger cluster sizes and RMS extent sizes will help prevent fragmentation and improve performance at the cost of some disk space.&lt;BR /&gt;Disk space is cheap.   Cheaper than user time.&lt;BR /&gt;&lt;BR /&gt;As mentioned, large log files are real killers.  Especially if they do not pre-allocate space and are being written to a bit at a time. Closing the utilities associated with Accountng.dat, errlog.sys and operator.log can creating new versions of these file, with a larger extent can really help over time.&lt;BR /&gt;</description>
      <pubDate>Mon, 20 Nov 2006 13:37:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900965#M80214</guid>
      <dc:creator>comarow</dc:creator>
      <dc:date>2006-11-20T13:37:30Z</dc:date>
    </item>
    <item>
      <title>Re: Fragmentation of disk drive</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900966#M80215</link>
      <description>This might be a little off topic, but in the days before defrag utils, I'd perform a restore from an image backup.  Doesn't this still apply?&lt;BR /&gt;&lt;BR /&gt;Jim</description>
      <pubDate>Mon, 20 Nov 2006 13:39:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900966#M80215</guid>
      <dc:creator>Jim Lahman_1</dc:creator>
      <dc:date>2006-11-20T13:39:38Z</dc:date>
    </item>
    <item>
      <title>Re: Fragmentation of disk drive</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900967#M80216</link>
      <description>@Jim,&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;This might be a little off topic, but in the days before defrag utils, I'd perform a restore from an image backup. Doesn't this still apply?&lt;BR /&gt;&amp;lt;&amp;lt;&amp;lt;&lt;BR /&gt;&lt;BR /&gt;Yeah, it still applies... _IF_ you can afford the off-line time (of for system disk, Down time).&lt;BR /&gt;Many, many of the sites using VMS nowadays, are doing that BECAUSE of the 24*7, or 24*365 capabilities, and _THEN_ that option is a little bit out of the question.&lt;BR /&gt;&lt;BR /&gt;Just my EUR 0,02&lt;BR /&gt;&lt;BR /&gt;(notice, even the decimal COMMA is un-english!)&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Mon, 20 Nov 2006 14:18:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900967#M80216</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2006-11-20T14:18:49Z</dc:date>
    </item>
    <item>
      <title>Re: Fragmentation of disk drive</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900968#M80217</link>
      <description>Before you start scheduling downtime, is fragmentation having an impact?  Use monitor to check window turn rate and split transfer rates:&lt;BR /&gt;&lt;BR /&gt;$ monitor fcp&lt;BR /&gt;$ monitor io&lt;BR /&gt;&lt;BR /&gt;A disk can be severely fragmented and not create a performance issue if it doesn't create significant i/o.  Purging log files is usually enough to defrag a system disk.  &lt;BR /&gt;&lt;BR /&gt;Andy</description>
      <pubDate>Mon, 20 Nov 2006 14:29:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900968#M80217</guid>
      <dc:creator>Andy Bustamante</dc:creator>
      <dc:date>2006-11-20T14:29:01Z</dc:date>
    </item>
    <item>
      <title>Re: Fragmentation of disk drive</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900969#M80218</link>
      <description>Don't forget to monitor the "maximum free extent" on the disk. This is what gives most problems (on my site anyway). Under 10000 blocks is a red alert here. And I have seen that during defragments, this value was VERY low, so a threat to the well being of the production environment.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 21 Nov 2006 04:31:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900969#M80218</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2006-11-21T04:31:28Z</dc:date>
    </item>
    <item>
      <title>Re: Fragmentation of disk drive</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900970#M80219</link>
      <description>You can directly check fragmentation state of any file by executing&lt;BR /&gt;&lt;BR /&gt;$ PIPE DUMP/HEADER &lt;FILE_NAME&gt;| TYPE SYS$INPUT /PAGE&lt;BR /&gt;&lt;BR /&gt;and look for the list of retrieval pointers looking like this:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Map area&lt;BR /&gt;    Retrieval pointers&lt;BR /&gt;        Count:        36        LBN: 1280646&lt;BR /&gt;&lt;BR /&gt;Each "Count ... LBN..." line is one fragment. Multiple "Count:..."lines mean fragmented file. I have seen files with hundreds and hundreds of pointers to fragments...&lt;BR /&gt;&lt;BR /&gt;Ziggy&lt;/FILE_NAME&gt;</description>
      <pubDate>Wed, 22 Nov 2006 20:26:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900970#M80219</guid>
      <dc:creator>Ziggy Filek</dc:creator>
      <dc:date>2006-11-22T20:26:19Z</dc:date>
    </item>
    <item>
      <title>Re: Fragmentation of disk drive</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900971#M80220</link>
      <description>DFU is a really easy and effective tool here.&lt;BR /&gt;&lt;BR /&gt;$define dfu$nosmg yes&lt;BR /&gt;$dfu sea/frag=min=100 sys$disk:&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; I have seen files with hundreds and hundreds of pointers to fragments...&lt;BR /&gt;&lt;BR /&gt;I'll see your hundreds of pointers and raise you hundred fifty headers.&lt;BR /&gt;&lt;BR /&gt;:-)&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; $ PIPE DUMP/HEADER &lt;FILE_NAME&gt;| TYPE SYS$INPUT /PAGE&lt;BR /&gt;&lt;BR /&gt;Too much work! Try this:&lt;BR /&gt;&lt;BR /&gt;$ perl -e "foreach (`dump/head/bloc=cou=0 $ARGV[0]`) { $h++ if /^Check/; $m++ if /Count:/} print qq($h headers, $m pointers.\n)" &lt;FILE-NAME&gt;&lt;BR /&gt;&lt;BR /&gt;More :-)&lt;BR /&gt;Hein.&lt;BR /&gt;&lt;/FILE-NAME&gt;&lt;/FILE_NAME&gt;</description>
      <pubDate>Wed, 22 Nov 2006 22:01:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/fragmentation-of-disk-drive/m-p/3900971#M80220</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2006-11-22T22:01:17Z</dc:date>
    </item>
  </channel>
</rss>

