Hi, Thanks for getting back to me
I tried what you mentioned, and... /dev/osst0 does exist, but if I try something like mt -f /dev/osst0 setblk 0 I get mt: /dev/osst0: no such device Which seems strange (to me anyway))... Just to report the detail, here's the ls -l for /dev/*st0 crw-rw---- 1 roor root 9, 128 Oct 26 2002 /dev/nst0 crw-r--r-- 1 roor root 206, 0 Oct 26 2002 /dev/osst0 crw-rw---- 1 roor root 9, 0 Oct 26 2002 /dev/st0 Once again, thanks in advance for any help Cheers Paul ----- Original Message ----- From: "Charlie Brady" <[EMAIL PROTECTED]> To: "Edwin Huffstutler" <[EMAIL PROTECTED]> Cc: "Paul Murphy" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, October 06, 2003 6:19 PM Subject: Re: [flexbackup-help] Problem with tape drive > > On Mon, 6 Oct 2003, Edwin Huffstutler wrote: > > > Does > > mt -f /dev/nst0 setblk 32768 > > > > give an error? How about > > > > mt -f /dev/nst0 setblk 0 > > > > (variable block size)? > > > > See the "n" answers regarding the ADR2 drives and block sizes here: > > http://www.linuxtapecert.org/drives.php. This does not inspire confidence, > > but I don't have one of those drives. Keep playing with it..... maybe try > > just a simple "1024" for the mt_blksize? > > > > > > (BTW: you want to use /dev/nst0 not /dev/st0) > > Actually, for the Onstream, you may want /dev/nosst0. Onstream appear not > to understand open source, and forked the st driver, rather than add on > option to it to handle their non-standard protocol. Hence osst.o (for > Onstream st.o). > > Beware that prior to RedHat 9, RH RPMs didn't include /dev/nosst0, just > /dev/osst0. > > -- > Charlie > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ flexbackup-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/flexbackup-help
