In regard to: Re: [Networker] Can you "scanner" a SDLT tape in a SDLT-600...:

You give NetWorker a device path (e.g. /dev/nst0) and you tell it what
type of drive is associated with that device path.  NetWorker opens that
path (possibly setting a particular block size) and flings data into it
until NetWorker gets a write error, at which point it stops writing and
says "tape full".

Yeah, I've noticed. :-) I'd like to have a mail notification when
something like that happens, but haven't been able to figure out how to
get that notification set up (a "media write error" notification, not a
"media full" notification, which would be a normal sequence of events)

Again, how's it supposed to know the difference?  They both look the same
to NetWorker -- a write error.

When NetWorker gets a write error on a volume, it marks it full, since it
has no way of knowing whether the write error was because of a bad spot on
tape or because the end of tape (EOT) was reached.

If you want to find volumes that probably have bad spots on them, you use
mminfo to look for volumes that are marked full but have less than some
threshold amount of data on them.

Tim
--
Tim Mooney                                             Tim.Mooney AT ndsu DOT 
edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER