That was it, forgot status. Fixing now.
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of white jeff Sent: Monday, June 08, 2015 1:38 PM To: [email protected] Subject: Re: [ADSM-L] server out of storage space when really not missing vmware backups Gary That depends on the volume status. If FILLING, then it is eligible to be written to. Example a volume in FILLING status which is 75% utilised has 25% free space. Therefore a candidate for wring to. If FULL, the volume was 100% full at one stage. The volume remains in that state until all of the space is reclaimed and is 0% full, then PENDING state and finally SCRATCH. Example, a 75% utilised volume that is in FULL state is NOT eligible to be written to. Hitting maxscratch indeed renders the storage pool full, which it effectively is. select volume_name, status, pct_utilized, pct_reclaim from volumes order by 2,3 This will show you which volumes are in FILLING state and therefore eligible to be written to. What are your reclaim values - are you freeing up tapes via reclaim in the VM pool? On 8 June 2015 at 18:15, Lee, Gary <[email protected]> wrote: > My question here is that 59 out of 195 volumes in the pool are less than > 75% utilized. > Shouldn't tsm fil them before declaring itself out of space? > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of > David Ehresman > Sent: Monday, June 08, 2015 12:07 PM > To: [email protected] > Subject: Re: [ADSM-L] server out of storage space when really not missing > vmware backups > > Maxscratch defines how many scratch volumes you can have in a > storagepool. When you reach maxscratch, assuming you do not have volumes > predefined, you are by definition out of data storage space regardless of > how much space is in your filesystem. > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of > Lee, Gary > Sent: Monday, June 08, 2015 10:32 AM > To: [email protected] > Subject: [ADSM-L] server out of storage space when really not missing > vmware backups > > Tsm server 6.2.5 > TDP for vmware 6.4 > > I have the vmware data pool defined as a sequencial file pool, to > facilitate migration. > > However, last night the server claimed it was out of data storage space, > but there is 18% of a 14 tb pool free. > > I checked, and the only limit reached was maxscratch. > > Is there a good way around this? > > We want to migrate to server 7.x, but could not get an install failure > resolved on RHEL 6.5 for server version 7.1.1. > > I have increased maxscratch, but this cannot go on indefinitely. >
