From owner-freebsd-questions Fri Oct 31 20:31:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA28928 for questions-outgoing; Fri, 31 Oct 1997 20:31:28 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA28923 for ; Fri, 31 Oct 1997 20:31:25 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.7) with SMTP id UAA19943; Fri, 31 Oct 1997 20:31:20 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Fri, 31 Oct 1997 20:31:20 -0800 (PST) From: Doug White Reply-To: Doug White To: Palle Girgensohn cc: freebsd-questions@FreeBSD.ORG Subject: Re: rdump and blocksize? In-Reply-To: <34593BC3.41335BA2@partitur.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 31 Oct 1997, Palle Girgensohn wrote: > I've been browsing though the mail archive looking for tips on setting a > good blocksize for rdump. My problem is the same as for many others: > rdump is slow, around 48KB/s. > I have checked the network cards, and troughput is very good otherwise > (using for example rcp). Some recommended raising the blocksize, which > seems like the right thing to do. Only, 64 KB is the limit. I don't see > it help very much. Often 10KB or 32 KB were recommended as good values. > > So here's my main quiestion: > Do I have to fine tune the blocksize to some magic value where it's > synced with network & tape drive, or is bigger blocks == faster? I tried > 10 KB, and didn't see any difference. Finding the blocksize is a bit of a black art since it depends on several factors: 1. Disk speed 2. Disk subsystem overhead 3. I/O bus bandwidth 4. Network bandwidth 5. Dump device speed ..... You get the idea. The best thing to do is to try different values and use what works best on your system. > And the -B, is it only for calculating tape usage? Yes. Along with the -b option it specifies the size of the tape. If you're on 2.2.2 or later, you can use the -a option instead to have dump use the tape until it hits the end. > The tape is a Seagate using Travan TR-4, cartridge and compression, so > density is not very interresting, I presume. Its not just interesting, it's irrelevant! :-) Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major