As far as I could tell:
- the new filespace for Project 612 is up (you will have to check where your files are - they may still be in the original space)
- the system sees 64 CPUs again
- when restarting, disk problems necessitated a rebuild of the newly configured /temporary/saswork1, wiping all files previously written to it.
I will investigate further.