Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 24 Aug 2004 12:04:53 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Very slow SCSI tape drive with cygwin/Win2kPro Message-ID: <20040824100453.GF27978@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200408231840 DOT 52007 DOT whn AT lopi DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408231840.52007.whn@lopi.com> User-Agent: Mutt/1.4.2i On Aug 23 18:40, Bill Nugent wrote: > mt -f /dev/nst0 setblk 8192 > tar -tf /dev/nst0 -b 32 tar --help, especially the -b option. > Block size does not seem to be a factor. I've tried 8k, 16k and 32k > (over 32k doesn't work for some reason). Did you have a look into the `mt status 3' output below? Other than that, you will notice that Cygwin is always slower than native techniques since there's a whole layer of POSIX functionality on top of the Win32 stuff. > $ mt -f /dev/st0 status 3 > drive type : 01 (Unknown type of tape device) > tape capacity : 102629376 KB remaining : 8861696 KB > current file : 0 active partition : 0 > current block : 0 cur logical block: 0 > General status bits on (45030000): > BOT WR_PROT ONLINE IM_REP_EN HW_COMP > min block size : 2 max block size : 32768 ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/