On Sun, 2007-08-19 at 22:14 +0200, Matthias Schönborn wrote:
let me put it like this. the behaviour of disks & filesystems never
ceases to amaze me in its unpredictability. i recently built up a
machine for someone that had two identical samsung disk drives in it.
they were both formatted in the same way to hold ext3 filesystems. One
had the OS installed on it, the other was empty. the systemdisk was
incapable of recording even 6 tracks at once without this error; the
other disk could do 64 without breaking much of sweat. the difference? i
don't know, but if i had to point a finger i'd point it at the OS
install fragmenting the disk allocation in ways that made it impossible
for the filesystem to allocate new, large, contiguous blocks in an
efficient way. this is just a guess. i really don't know the reason.
the error message from ardour means *precisely* what it says: ardour was
trying to read/write data from/to the disk, and it was not happening
quickly enough. this could be the fault of the disk h/w, the filesystem,
the disk controller, or the kernel. or all of them.