From owner-freebsd-hackers Sun Mar 19 18:13:55 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA07290 for hackers-outgoing; Sun, 19 Mar 1995 18:13:55 -0800 Received: from hutcs.cs.hut.fi (root@hutcs.cs.hut.fi [130.233.192.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA07284 for ; Sun, 19 Mar 1995 18:13:53 -0800 Received: from shadows.cs.hut.fi by hutcs.cs.hut.fi with SMTP id AA20639 (5.65c8/HUTCS-S 1.4 for ); Mon, 20 Mar 1995 04:13:46 +0200 From: Heikki Suonsivu Received: (hsu@localhost) by shadows.cs.hut.fi (8.6.10/8.6.10) id EAA03300; Mon, 20 Mar 1995 04:13:50 +0200 Date: Mon, 20 Mar 1995 04:13:50 +0200 Message-Id: <199503200213.EAA03300@shadows.cs.hut.fi> To: guido@IAEhv.nl (Guido van Rooij) Cc: freebsd-hackers@freefall.cdrom.com In-Reply-To: guido@IAEhv.nl's message of 19 Mar 1995 20:12:52 +0200 Subject: restore times veryyyy long Organization: Helsinki University of Technology, Otaniemi, Finland Sender: hackers-owner@FreeBSD.org Precedence: bulk We did a restore of a 1.2 gig partition. The restore was done from a dat tape to a completely empty partition. It took 10(!) hours. Can anybody explain why this should take so long? What drive you have? We have got a WangDAT 3400DX and see similar problem, about 12KB/s read performance, while writes work normally. The same drive on a Sun SS10 works considerably better even though it is slower reading than writing. Both Buslogic 445S and Adaptek 1542 behave similarly. Restores have been so infrequent that I haven't had time to look at this more closely, but it might be useful to get it solved. We also saw cache getting disabled on a HP drive, apparently by changing from read to write or vice versa, don't remember any more which way it was. I understood that this was a bug in the drive. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN