> You might try using even larger blocks, like 32k, or playing with the
> parameters to "tunefs(8)". 
using 32k blocks improves situation a bit, but there still are lockups i 
described before. maximum writing speed i could get from dd writing to a 
file is something about 8mb/s... so that's not much when compared to 
20mb/s when writing directly on the device or 18mb/s i can get from the 
copy/move on faster disk in midnightcommander...

> It might not be a bad idea to go ahead and
> build a file system on the new disk using a 1.6.2 floppy, just to rule
> out the hardware completely. 
i'll try the 1.6.1 i have here... i'm just wondering whether it is 
possible to manage without a need to reboot with the floppy/cdrom. can i 
somehow mount the installation cdrom/floppies to have access to the 
older versions of the programs that are used for installation? (i guess 
it is file boot.i386 that contains these files...

> You said the disks are identical -- could
> you use "dkctl" to verify that the write cache is on for the new disk?
yes, disks are identical pieces of hardware, however differently partitioned
"SMALL" - fast disk
/dev/wd0d: read cache enabled
/dev/wd0d: write-back cache enabled
/dev/wd0d: read cache enable is not changeable
/dev/wd0d: write cache enable is changeable
/dev/wd0d: cache parameters are not savable
"LARGE" - slow disk
/dev/wd1d: read cache enabled
/dev/wd1d: write-back cache enabled
/dev/wd1d: read cache enable is not changeable
/dev/wd1d: write cache enable is changeable
/dev/wd1d: cache parameters are not savable

regards,

-- 
Lubos
_@_"