A few were readonly. However, that did not explain all of them by a long way. Others are filling.
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Thursday, September 19, 2013 4:05 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] strange tape handling What is the access setting on the tape, is it READWRITE? And is status FULL or FILLING? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee, Gary Sent: Thursday, September 19, 2013 2:05 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] strange tape handling Tsm server 6.2.4 on RHEL 6 Tape storage pool on ts1120 tapes, collocation set to group. Node libprint does not belong to any group. Its data is now on two volumes. First volume has estimated capacity 1 tB. It is 1.4% full. This morning, tsm was migrating its data from disk pool to tape. It pulled another scratch to store systemstate data even though the original volume was only 1.4% full as stated above. What is up with this. This is causing my scratch tapes to be eaten up to no purpose.
