Table of contents
Combined revision comparison
...
During unrelated tests at MPIfR, unfortunately the filesystem metadata on 1 out of the 8 disks got erased, i.e., "erased" part of the module. During a later trip to APEX the missing 'GMVA_slot2' files of that disk were copied out from the still existing module there. These were then integrated back into BHC%0141. The missing 'data' files of that disk were less trivial to recover. Nevertheless, full recovery was successful. ModuleThe BHC%0141 contains the full original data again. For future reference the steps were:
...
Version from 11:06, 19 Dec 2024
...
During unrelated tests at MPIfR, unfortunately the filesystem metadata on 1 out of the 8 disks got erased, i.e., "erased" part of the module. During a later trip to APEX the missing 'GMVA_slot2' files of that disk were copied out from the still existing module there. These were then integrated back into BHC%0141. The missing 'data' files of that disk were less trivial to recover. Nevertheless, full recovery was successful. The BHC%0141 contains the full original data again. For future reference the steps were:
...
Current version
...
During unrelated tests at MPIfR, unfortunately the filesystem metadata on 1 out of the 8 disks got erased, i.e., "erased" part of the module. During a later trip to APEX the missing 'GMVA_slot2' files of that disk were copied out from the still existing module there. These were then integrated back into BHC%0141. The missing 'data' files of that disk were less trivial to recover. Nevertheless, full recovery was successful. Module BHC%0141 contains the full original data again. For future reference the steps were:
...
