On Apr 16, 2007, at 2:42 AM, Robert Ouzen Ouzen wrote:
After receiving for a Windows client 2003 Tsm version 5.3.4.8
client an output of Failed 12, I checked the error log and saw
this: (a lot of them ..)
16-04-2007 01:00:52 fioScanDirEntry(): *** Skipping corrupted file/
directory: '\\?\tsmlvsa_Volume{1840fc90-8f7e-11db-8be1-806e6f6e6963}
\PHP\sessiondata'
...
Robert -
To the best of my knowledge, all such instances of this messages
discussed on the List have been TSM accurately uncovering file system
corruption, and - surprise, surprise - the platform has always been
Windows. The symptoms suggest that chkdsk or an equivalent
commercial disk fixit program need to be run.
Richard Sims
