From owner-freebsd-stable@FreeBSD.ORG Thu Oct 9 04:08:12 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 802FF7A6 for ; Thu, 9 Oct 2014 04:08:12 +0000 (UTC) Received: from mithlond.kdm.org (mithlond.kdm.org [70.56.43.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "A1-33714", Issuer "A1-33714" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BD4CC79 for ; Thu, 9 Oct 2014 04:08:11 +0000 (UTC) Received: from mithlond.kdm.org (localhost [127.0.0.1]) by mithlond.kdm.org (8.14.9/8.14.9) with ESMTP id s993mJcI030528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 8 Oct 2014 21:48:19 -0600 (MDT) (envelope-from ken@mithlond.kdm.org) Received: (from ken@localhost) by mithlond.kdm.org (8.14.9/8.14.9/Submit) id s993mJts030527; Wed, 8 Oct 2014 21:48:19 -0600 (MDT) (envelope-from ken) Date: Wed, 8 Oct 2014 21:48:19 -0600 From: "Kenneth D. Merry" To: Stefan Huerter Subject: Re: LSI 1030 and LTO-3 won't work Message-ID: <20141009034819.GA30406@mithlond.kdm.org> References: <54358D99.5090403@guckux.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54358D99.5090403@guckux.de> User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (mithlond.kdm.org [127.0.0.1]); Wed, 08 Oct 2014 21:48:19 -0600 (MDT) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS autolearn=ham autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mithlond.kdm.org Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Oct 2014 04:08:12 -0000 On Wed, Oct 08, 2014 at 21:16:41 +0200, Stefan Huerter wrote: > Guckux > > I have problems with following configuration: > FreeBSD whisky 10.1-RC1 FreeBSD 10.1-RC1 #0 r272711M: Tue Oct 7, > LSILogic 1030 Ultra4 Adapter > Sun StorEdge C2 - LTO-3 library > > I've included the mpt-module to load at boot time in loader.conf. > > part from dmesg: > mpt0: port 0xc400-0xc4ff mem > 0xff9a0000-0xff9bffff,0xff980000-0xff99ffff irq 23 at device 2.0 on pci5 > mpt0: MPI Version=1.2.14.0 > mpt1: port 0xc800-0xc8ff mem > 0xff9c0000-0xff9dffff irq 20 at device 2.1 on pci5 > mpt1: MPI Version=1.2.14.0 > > (sa0:mpt0:0:5:0): 32768-byte tape record bigger than supplied buffer > (sa0:mpt0:0:5:0): 32768-byte tape record bigger than supplied buffer > > I've tried to resize the blocksize to 10240 via mt blocksize 10240. > > Nothing works - dump and tar... > dump reports shortly, that the End of tape is detected, tar reports > "write error". > > With the same controller no Problem with Backup Exec under Windows, or > Solaris with EMC networker. > > Hugh? > Any hints for me? Or can I give you some other informations, which you need? The error messages above usually indicate that you're trying to read a block from the tape (in this case a 32K block) that is bigger than the blocksize that you specified. But it can also happen on a write to a tape when you're in fixed block mode and you try to write less than the blocksize. What does 'mt status' show? If it shows 32KB blocks, then that may be your problem. What blocksize are you using with tar and dump? (I believe they default to 10240 bytes.) It's generally easier to run in variable blocksize mode. You can specify variable blocksize with 'mt blocksize 0'. You can verify which mode you're in with 'mt status'. For instance, this tape drive is in variable block mode: Mode Density Blocksize bpi Compression Current: 0x5a:LTO-6 variable 384607 0xff ---------available modes--------- 0: 0x5a:LTO-6 variable 384607 0xff 1: 0x5a:LTO-6 variable 384607 0xff 2: 0x5a:LTO-6 variable 384607 0xff 3: 0x5a:LTO-6 variable 384607 0xff --------------------------------- Current Driver State: at rest. --------------------------------- File Number: 0 Record Number: 0 Residual Count -1 I would try something like this: mt rewind mt blocksize 0 mt status (verify that it says variable block mode) dump -C 16 -b 64 -0ua -f /dev/nsa0 / That specifies: - 16MB read cache size (for reading the disk) - 64K output blocksize - level 0 dump - update /etc/dumpdates - write until the end of tape - use the non-rewound tape device - dump the root partition It is generally better to write to the tape drive with the largest blocksize that your tape drive and controller support. You'll get better throughput that way. The tape driver in FreeBSD 10 will not allow you to read or write a blocksize that your drive and controller don't support. To see what they support, try: sysctl kern.cam.sa.0 maxio is the what we think you can effectively write given the limits of the system and the controller. cpi_maxio is what the controller claims to support. Ken -- Kenneth Merry ken@FreeBSD.ORG