Hide Forgot
Created attachment 527796 [details] Not-so-useful log Description of problem: The benchmark feature of the Disk Utility application seems to randomly crash when measuring the write rate of a relatively small device. Version-Release number of selected component (if applicable): 1.0.4-1.fc16 How reproducible: Highly when the volume is "very" small (< ~7G), less when it's bigger. Steps to Reproduce: 1. Launch Disk Utility (/usr/bin/palimpsest), 2. Start a Read/Write Benchmark on a small drive, or a small RAID array. Actual results: The software complains that the "helper" exited with an error after trying to write something while there was no space left on the device. Expected results: Benchmark ends and the Disk Utility displays the results. Additional info: Reading helpers/job-drive-benchmark.c, it seems that measure_write_transfer_rate() can write past the end of the device: While the size of the device is retrieved correctly, neither the sample size nor the number of samples is adjusted according to it. Thus, if the size of the device is less than sample_size * num_samples, the program will pick overlapping samples. While this poses no problem for the first samples, the last ones will "overflow" past the end of the device. The reason why the results are quite non-deterministic is that the buffer_size (sample_size) *is* adjusted in guesstimate_optimal_buffer_size(), but not according to the size of the device itself: rather, it is used to measure the read rate of a single sample in order to estimate a sorta optimal buffer_size so that the benchmark doesn't take more than 30 seconds. This means that in theory, the slower a device is, the less likely it is to hit the bug. In order to complete the benchmark reliably, the minimum capacity of a device capable of reading at over 666.6MiB/s would be 20000MiB, and less if the device is slower (at least if I got it right). Solutions include modifying guesstimate_optimal_buffer_size() to adjust the buffer_size according to [device] size or implementing a new guesstimate_optimal_num_samples() routine so that buffer_size * num_samples < size (or a hybrid of those).
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.