Date: Tue, 11 Feb 1997 22:29:55 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: plm@xs4all.nl (Peter Mutsaers) Cc: freebsd-bugs@freefall.freebsd.org Subject: Re: kern/2698: scsi tape driver problem Message-ID: <Mutt.19970211222955.j@uriah.heep.sax.de> In-Reply-To: <199702111730.SAA05774@plm.xs4all.nl>; from Peter Mutsaers on Feb 11, 1997 18:30:59 %2B0100 References: <199702101950.LAA20963@freefall.freebsd.org> <Pine.BSF.3.95q.970210124628.24299G-100000@hydrogen.nike.efn.org> <199702110000.BAA00374@plm.xs4all.nl> <Mutt.19970211094550.j@uriah.heep.sax.de> <199702111730.SAA05774@plm.xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
As Peter Mutsaers wrote: (new firmware) > That'll be difficult. I bought it years ago in a second hand shop. > I may have to learn to live with it (I use QIC 525 mostly anyway). Ask Wangtek, or see if they have a Web server. > But I still wonder why I see this problem under FreeBSD, and not under > Linux. Perhaps Linux `slices' the requests into 512-byte chunks at driver level? FreeBSD's driver relies on the drive honoring the blocksize setting, and writes whatever you pass in the write(2) syscall in a single SCSI write operation. With a variable-blocking tape, this basically causes the tape block to grow to just this size. With a fixed-length tape, the tape drive itself slices the request. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970211222955.j>