zftape Resource of device busy

HI,

I have been using ftape-20020317 for some time now with Amanda as my 
backup system. When I try to use amlabel to relabel a tape I get the 
following errors:

Jul 11 12:16:01 stud kernel: [217] 0  zftape-write.c (_zft_write) - check_write_access(zftape, req_len, &zftape->volume, &zftape->pos, zftape->blk_sz) failed: -22.
Jul 11 12:21:55 stud kernel: [232] 0  zftape-write.c (_zft_write) - check_write_access(zftape, req_len, &zftape->volume, &zftape->pos, zftape->blk_sz) failed: -22.
Jul 11 12:25:42 stud kernel: [008] 0 zftape-init.c (zft_open) - failed: already busy.
Jul 11 12:25:44 stud kernel: [009] 0 zftape-init.c (zft_open) - failed: already busy.
Jul 11 12:25:48 stud kernel: [010] 0 zftape-init.c (zft_open) - failed: already busy.
Jul 11 12:25:56 stud kernel: [011] 0 zftape-init.c (zft_open) - failed: already busy.

.
.
.

I don't know what I did to open zftape up, but I cannot remove it by using the rmmod command.  I tried to find out what user was using the modules by running fuser -u but nothing came up.  Now, for some history: I had to consolidate 4  hard drives onto 1 the other day and I have experienced some permission problems with other programs which I thought that I got straightened out.  Could this be the culprit?  TIA.
-- 
Trevor Morrison
Hailix, LLC	
[email protected]


-
To unsubscribe from this list: send the line "unsubscribe linux-tape" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html