From owner-freebsd-current@FreeBSD.ORG Mon Dec 23 10:45:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6A58AEBA for ; Mon, 23 Dec 2013 10:45:18 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3BA89101D for ; Mon, 23 Dec 2013 10:45:17 +0000 (UTC) Received: from [192.168.1.73] (254C2F09.nat.pool.telekom.hu [37.76.47.9]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id rBNAj7Y3082383 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 23 Dec 2013 02:45:09 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <52B8142E.8090104@freebsd.org> Date: Mon, 23 Dec 2013 11:45:02 +0100 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Konstantin Belousov , Manfred Antar Subject: Re: vfs_bio.c revision 259200 breaks writing to tape drive on current References: <201312221754.rBMHssMv004688@pozo.com> <20131223073102.GA59496@kib.kiev.ua> In-Reply-To: <20131223073102.GA59496@kib.kiev.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Dec 2013 10:45:18 -0000 On 12/23/13, 8:31 AM, Konstantin Belousov wrote: > On Sun, Dec 22, 2013 at 09:54:49AM -0800, Manfred Antar wrote: >> The change to vfs_bio.c in revision 259200 breaks writing to scsi tape drive on i386 and sparc64 on current. >> I don't have any other machines to test on. >> here is example: >> >> r259199: >> (/)4794}mt rew >> (/)4795}tar cvf /dev/sa0 kernel >> a kernel >> >> r259200: >> (/)4781}mt rew >> (/)4782}tar cvf /dev/sa0 kernel >> a kerneltar: Write error >> >> the changes between the two revisions: >> line 3682 removed: >> >> bp->b_resid = bip->bio_resid; /* XXX: remove */ >> >> I noticed this when trying to do a dump and getting end of tape error. >> tried different tape drives , different cables no change. >> backed out r259200 to 259199 and everything works as before. >> Manfred > Show me the kdump of the tar commands on both revisions. I had to do all sorts of special handling back in the 1.x days to get tape drives to work correctly. length and resid ahndlign were susceptible to failure in hte various different schemes of how tape drive s shoud work (variable lenght records, fixed length and ather variations I forget) .