I've seen this behavior when problem occurs using the tape, for example, a 
mount fails, a label read error occurs, etc.  You might want to go bck through 
the activity log and see what happened last with these volumes.

Jackie Balboni wrote:

> Strange happenings with tapes staying in libv with a status of private and 
> last use of data. Theses tapes however: belong to no storage pool  and have 
> no data on them. We are at the latest release of Atape driver, ADSM 3.1.1.3 
> server on Aix.  The only way I can get them back to scratch is to assign them 
> to a dummy storage pool and delete them. Has anyone seen this. We have a 3575 
> L32.