From owner-freebsd-current Tue Mar 31 11:00:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19114 for freebsd-current-outgoing; Tue, 31 Mar 1998 11:00:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fddi.Simon-Shapiro.ORG [206.190.148.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA18985 for ; Tue, 31 Mar 1998 10:59:53 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 2355 invoked from network); 31 Mar 1998 19:09:01 -0000 Received: from localhost.simon-shapiro.org (HELO sendero-fxp0.simon-shapiro.org) (@127.0.0.1) by localhost.simon-shapiro.org with SMTP; 31 Mar 1998 19:09:01 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-032398 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199803311851.LAA12117@pluto.plutotech.com> Date: Tue, 31 Mar 1998 11:09:01 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: "Justin T. Gibbs" Subject: Re: CONTINUED problems: Restore/Dump broken? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 31-Mar-98 Justin T. Gibbs wrote: >>This is in the current current. Not in CAM. We still have to use it >>until >>we all convert to CAM, CAM is in the main branch, etc. > > CAM should have no effect on this problem. The old driver was able > to write the blocksize you told it correctly too. Used to be. It used to be working correctly. It does not work correctly now. >>As I said before, this happens with cpio too. You do: >>cd /etc;find . | cpio -H newc -ov -C 65536 -O /dev/nst2.2 > > I never use a sub mode tape device and the driver may well be doing > something hokey. I also don't have any nst devices. Only nrst and rst. > 8-) I tried each and every one of the possible entry points. None of them works correctly anymore. The submode is meamingless here. > The nrst2 device should have the default density for the device which, > for DDS-* drives should be what you want. Density is not the problem. Data corruption is. When reading with dd or cpio, you get fragments of reality, which shows that the bits are correct. I suspect the blocking scatter/gather logic to have gone south. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message