On 9/5/07, <b class="gmail_sendername">Michael T. Dean</b> <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 09/05/2007 10:45 AM, John Goerzen wrote:<br><snip><br>Basically, I had 200GB of data on the disk that was severely<br>fragmented. It took me 10 hours to read that data from the disk and<br>write it to another local disk (on another bus). That means the average
<br>read performance was at least 5.5MB/sec--far more than enough for the<br>max 19.39Mbps (2.4MB/sec) of my OTA ATSC recordings. However, while<br>/most/ parts of most shows played perfectly well, there were sections<br>
where the fragmentation caused read performance to drop to the point<br>that it would play 1 second, then pause for 5-10 seconds, then play 1<br>second. Once I copied the data to another drive and moved it back, the<br>shows played perfectly, and without issue.
<br></snip></blockquote><div><br>Now you got me worried. What tool and more importantly what metrics do you use to figure out if disk/io is having hard time? iostats?<br><br>Since I just added dual hd receiver I'll most likely hit the SD/HD scenario in the near future.
<br></div></div>