Looks like I did not send you the results for VPB681. My mistake. There were 6 bad files reading VPB681 on a "C" drive and 5 bad files reading on a "D" drive. files
918 1010 1069 1099 1127. These files are marked bad in enstore.
VPB681 CDMS133663936400000 3145205106 0000_000000000_0000918 active
VPB681 CDMS133664643700000 3509823114 0000_000000000_0001010 active
VPB681 CDMS133664871900001 3512245966 0000_000000000_0001069 active
VPB681 CDMS133664968800000 3511495195 0000_000000000_0001099 active
VPB681 CDMS133665064600000 3546033623 0000_000000000_0001127 active
On 5/26/2015 6:17 PM, Chih-Hao Huang wrote:
I do not have any information about VPB681.
If you had sent me cloning result of VPB681, please send me again. Sorry about that.
Files on the other volumes are all user files and are considered lost.
We are in the process of notifying users.
We have not heard complaints, yet.
On May 26, 2015, at 1:04 PM, george <firstname.lastname@example.org> wrote:
Can you give me an update on finding files for VPB681 VPB636 VPC767 and VPB406?
#2 Updated by Chih-Hao Huang about 5 years ago
- Status changed from New to Accepted
- % Done changed from 0 to 90
All these 5 files are the only copy,
 no copies in disk instance
 no copies at any other PhEDEx sites
 never migrated (no LTO4 copies)
They have to be declared lost and be invalidated globally.
GGUS ticket for invalidation is: 113940.