When a file system just ~up & goes away~  TSM has no way of knowing WHY ???
might have died due to the media on which it resides died
might have gone away because someone just unmounted it
might have gone away because someone deleted it (for whatever reason)

So.... TSM freezes that entire filesystem until
        it comes back and resumes normal incremental processing
OR
        you purge it from an admin session...



Dwight E. Cook
Software Application Engineer III
Science Applications International Corporation
509 S. Boston Ave.  Suite 220
Tulsa, Oklahoma 74103-4606
Office (918) 732-7109



-----Original Message-----
From: Macmurray, Andrea (CAG-CC)
[mailto:Andrea.MacMurray AT CONAGRAFOODS DOT COM]
Sent: Friday, December 13, 2002 10:05 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: filespaces not deleted


Hello TSM'ers

With the danger that some of you might think I am not the sharpest tool in
the shed, there is one thing about filespaces I do not understand. Why are
there filespaces which will not expire?? If I rename a node and existing
files go under a new directory structure I would have expected that TSM
looks at the old filespaces as deleted and applies the normal retention
periods as specified in the Mgmtclasses for a deleted file. Is there
somebody out there who would be able to give me short explanation why this
is not happening and how I can identify all my dead filespaces out there. I
am pretty sure I do have tons of them out there.


Thanks
Andrea Mac Murray