From owner-freebsd-questions Mon Aug 10 22:15:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08361 for freebsd-questions-outgoing; Mon, 10 Aug 1998 22:15:48 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08356 for ; Mon, 10 Aug 1998 22:15:44 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id AAA08596; Tue, 11 Aug 1998 00:13:30 -0400 (EDT) Date: Tue, 11 Aug 1998 00:13:30 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Greg Lehey cc: FreeBSD-questions@FreeBSD.ORG Subject: Re: WangDat 3100 SCSI tape In-Reply-To: <19980811140316.R20188@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Aug 1998, Greg Lehey wrote: > > I got a new tape, to make sure that wasn't the problem. I have the > > density set to "X3B5/88-185A", Blocksize variable. I tried to tar my > > home directory onto it, which has more than 100M now. I get about 20 > > files into that, I get to a leftover kernel, and: > > > > .. > > .. > > chuckr/.login > > chuckr/.addressbook.lu > > chuckr/kernel > > tar: can't write to /dev/rst0 : Input/output error > > This should have been accompanied by a message on the console. Check > /var/log/messages to see it again. Here's the log message: Aug 11 00:18:09 moon st0: MEDIUM ERROR info:0x5f000 asc:c,0 Write error sks:80,1 Aug 11 00:18:09 moon st0: MEDIUM ERROR info:0x1 asc:c,0 Write error The same error seems to occur every time, even though the tape was changed out (twice). > > The fact that it listed the files doesn't mean that they got written. > tar first blocks them, and then tries to write the blocks to tape. > > > I'm doing this as root. I chose the density not because of the > > name, but because it numerically matched the density called out in > > the drive specification (I located that and downloaded it). > > Does it make any difference? What happens if you don't set a density > at all? I've set the density on /dev/st0ctl.0, to serve as a default on rst0. I don't set density in the tar command (I don't think I can). I've tried blocksizes of variable, 512, and 8192, and a couple different densities. Seeing as how the densities and blocksizes are defaulting, I don't see what "What happens if you don't set a density at all" could mean to me. I use as tar command "tar cvfb chuckr b #" (#=blocksize, or omitted for variable size blocks). chuckr is my home dir. > > Greg > -- > See complete headers for address and phone numbers > finger grog@lemis.com for PGP public key > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message