MAXSCRATCH is set to 999 but I was thinking along the lines of setting it to "0" as I don't want it to ever create scratch volumes (the filesystems only have a couple hundred MB free anyway, if that).
I think I have found the answer (prompted by Dale Jolliff). A lot of these volumes have recently been created but the filesystems that they reside on weren't added to the device class parameter so TSM wouldn't have used them - I have added them now and will see what happens tonight. Thanks all. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lloyd Dieter Sent: 22 December 2011 14:59 To: ADSM-L@VM.MARIST.EDU Subject: Re: [adsm] Re: Storage pool using scratch volumes instead of empty volumes Check and see what MAXSCRATCH is set to on xosatapool. If you predefined the volumes, it should probably be "0". Also, I've seen it do this if you remove a volume from the filesystem, then allocate new ones, but don't remove the old volume definition from within TSM (del vol XXXX). For some reason it tries to recreate them, even if maxscratch=0 and there are other volumes available. -Lloyd On 12/22/2011 06:26 AM, Copper, Steve wrote: > No - I get no volumes returned. > > tsm: TSM>q v stg=exosatapool stat=emp acc=reado,unav ANR2034E QUERY > VOLUME: No match found using this criteria. > ANS8001I Return code 11. > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of James R Owen > Sent: 22 December 2011 11:20 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Storage pool using scratch volumes instead of empty > volumes > > Steve, does this command also list your empty volumes: > q v stg=exosatapool stat=emp acc=reado,unav > -- > jim.o...@yale.edu > > On 12/22/2011 4:23 AM, Copper, Steve wrote: >> ... >> My question is: Why is this migration process creating scratch >> volumes in my filesystems when I have 666 (not made up,current >> figure!) empty volumes assigned to the storage pool? This has only >> recently started happening - before it would only create scratch >> volumes when it had run out of Empty volumes. >> ... >> Snip of "q vol stgpool=exosatapool" and grep'd for Empty >> >> /sata_vol_71/sata5058.d- EXOSATAPOOL SATACLASS 20.0 G >> 0.0 Empty >> /sata_vol_71/sata5059.d- EXOSATAPOOL SATACLASS 20.0 G >> 0.0 Empty >> /sata_vol_71/sata5060.d- EXOSATAPOOL SATACLASS 20.0 G >> 0.0 Empty >> /sata_vol_71/sata5061.d- EXOSATAPOOL SATACLASS 20.0 G >> 0.0 Empty >> ... > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security.cloud > service. > For more information please visit http://www.symanteccloud.com > ______________________________________________________________________ > > Western Power Distribution (South West) plc / Western Power > Distribution (South Wales) plc / Western Power Distribution (East > Midlands) plc / Western Power Distribution (West Midlands) plc > Registered in England and Wales Registered number: 2366894 (South > West) / 2366985 (South Wales) / 2366923 (East Midlands) / 3600574 > (West Midlands) > > Registered Office: Avonbank, Feeder Road, Bristol, BS2 0TB > > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. > > If you have received this email in error please notify > postmas...@westernpower.co.uk > ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________ Western Power Distribution (South West) plc / Western Power Distribution (South Wales) plc / Western Power Distribution (East Midlands) plc / Western Power Distribution (West Midlands) plc Registered in England and Wales Registered number: 2366894 (South West) / 2366985 (South Wales) / 2366923 (East Midlands) / 3600574 (West Midlands) Registered Office: Avonbank, Feeder Road, Bristol, BS2 0TB This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify postmas...@westernpower.co.uk
