Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 27 Jan 2003 15:17:02 +0100 From: Corinna Vinschen To: Gnuwin Subject: Re: problem accessing tape with tar on NT Message-ID: <20030127141702.GU2117@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: Gnuwin References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i On Mon, Jan 27, 2003 at 02:09:50PM -0000, Kris Thielemans wrote: > (The tapes were generated with block size 20. Does that happen to be the > default?). Once the typical blocksize was 5120 bytes on tapes. Today it's varying but many drive types support different block sizes. > - This version supports setting blocksize to 0 to enable the variable > blocksize feature since Cygwin V1.1.3. > ---------- > No clue what this means. With fixed blocksize (e. g. mt setblk 512), the NT tape driver reads and writes only blocks with the set blocksize (512 bytes in the above example). With variable blocksize (mt setblk 0), the NT tape driver reads any block, regardless of it's size on tape and writes a block with the size given to write(), this way potentially writing each block with another size (as far as the driver allows, see `mt status 2', "min block size" and "max block size"). Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/