Wolfgang Weisselberg wrote:
> Hi!
>
> Trying to kill the keyboard, [EMAIL PROTECTED] produced:
> > > Perhaps it would be easier if you included the relevant log file
> > > extracts ... there should be some entries that could pinpoint
> > > the error more closely.
>
> > I have just downloadet the latest version of 'unstable' and i get this
> > error:
>
> > root:~ $ ftformat --mode=auto --format-parameters qic-standard=TR-3
> > --omit-erase --discard-header
> > Calibrating tape length ... got 1079 segments
> > --format-parameters
> >
>qic-standard=0x83,format-code=4,floppy-head-max=52,floppy-track-max=254,segments-per-track=1079,tracks-per-tape=50,gap3=248,format-filler-byte=0x6b
> > Writing reference bursts ... done.
> > Formatting track 49, segment 53949
> > Error re-opening tape dev read/write: Device or resource busy
> > root:~ $
>
> So, what do the *logs* say?
>
> They should be found under /var/log, for example
> /var/log/messages or so (depends on your distribution, or
> more exactly, on /etc/syslog.conf. And please send that to
> the tape mailing list, the chances that someone knows are
> greater over there (I have set the Reply-To to aid you).
>
In the /var/log/messages:
Jun 7 23:23:09 localhost kernel: [016] ftape-io.c (ftape_report_configuration)
- TR-3 tape detected.
Jun 7 23:23:09 localhost kernel: [017] ftape-ctl.c (ftape_init_drive) - unknown
length QIC-3020 tape.
Jun 7 23:31:35 localhost kernel: [018] ftape-ctl.c (ftape_calibrate_data_rate) -
Highest FDC supported data rate: 1000 Kbps.
Jun 7 23:31:35 localhost kernel: [019] ftape-io.c (ftape_report_configuration)
- TR-3 tape detected.
Jun 8 05:10:39 localhost kernel: [020] zftape-init.c (zft_open) - failed: already
busy.
Jun 8 05:10:41 localhost kernel: [021] zftape-init.c (zft_close) - _zft_close failed.
--
Best regard
Jan Jozwiak, Denmark [EMAIL PROTECTED] | [EMAIL PROTECTED]
