Date: Tue, 9 Mar 1999 15:21:02 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> To: Tom Torrance at home <tom@tomqnx.com> Cc: chris@shenton.org, scsi@freebsd.org Subject: Re: 3.1-STABLE: nrsa0 T4000 doesn't honor "no rewind"? SCSI errs in logs Message-ID: <Pine.LNX.4.04.9903091332460.19746-100000@feral-gw> In-Reply-To: <m10KTZn-000I4EC@TomQNX.tomqnx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > This is a very well put argument for never doing ANYTHING at the driver > level that would cause a backup program to lose position information. > All very cogent arguments, except it is the broken applications here that the tape needs to be protected from. I'm writing (or reading) a tape. Something bad happens such that the tape driver loses a notion of where it is. Previously, nothing would happen- leading you to often either overwrite tapes or write them with an inconsistent set of filemarks. I added in a change that should (for most drives) eject the tape. This has turned out to be less than desirable for tapes that can't eject. Here's the alternative I'll offer: If the driver loses position, it will refuse to accept any I/O until either a rewind or an explicit space to EOD, or an unload occurs. This is somewhat trickier than other cases because I'll have to allow opens but no operations but the three mentioned. Opinions? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.04.9903091332460.19746-100000>