Wolfgang Weisselberg wrote:
> Hi!
>
> Trying to kill the keyboard, [EMAIL PROTECTED] produced:
> > ftmt: /dev/nqft0: Device or resource busy
>
> Looks like the ftape driver thinks something is still accessing
> your tape (it *is* properly inserted and detected by the drive?
> You gave the drive a minute or two?) and thus you are denied
> access. Either remove the offending processes, or try to unload
> the modules (bound to fail) and load them again (which then
> won't work) or you might have to reboot your machine. Sorry.
>
> -Wolfgang
I did give some time, as its a cron job and the tape has only been
removed a few times. my backup script is as follows:
ftmt -f /dev/nqft0 reten
ftmt -f /dev/nqft0 erase
ftmt -f /dev/nqft0 rewind
tar czvf /dev/nqft0 /
ftmt -f /dev/nqft0 rewind
perhaps there isn't enough time between the ftmt commands and the tar
command?
but judgung from the way the error reads, i think one of tar's child
processes is getting in the way. i was thinking, maybe it is backing up
/dev/nqft0 or something in proc and that is getting in the way.
ftmt: /dev/nqft0: Input/output error
tar: Removing leading `/' from absolute path names in the archive
lost+found/
mnt/
mnt/hda3/
...
mnt/hda3/home/colin/devel/muse1.9f3/
mnt/hda3/home/colin/devel/muse1.9f3/working.tar.gz
tar (grandchild): Cannot write to /dev/nqft0: Input/output error
tar (grandchild): Error is not recoverable: exiting now
ftmt: /dev/nqft0: Device or resource busy
i really need help with this. i'm sure i'm not doing anything unique -
hasn't anyone seen this problem?
all help appreciated,
nathan heagy
