Problem with a Beta filer not responding
By Ryan on Thursday 30 October 2008, 15:41 - alert - Permalink
Filer 18 (SATA) is currently not responding. We are going to progressively shut down the 375 servers that are on this filer in order to assure that there is no data corruption.
Our technical team is currently on location and working on solving the problem. We estimate that this will be resolved within an hour.
Please accept our apologies for any inconvenience this may have caused.
UPDATE: The problem has been identified as being hardware-related. Our technicians are currently making the necessary repairs. We will keep you informed of our progress. As a reminder, this hardware is no longer used on the final release architecture.
UPDATE: We have built a new filer, and VMs are now restarting on it. We are watching your fscks, this seems okay everywhere. An overload of the filer was anticipated for the evening, though has been absorbed nicely. We will soon be migrating this filer to SAS.
Our technical team is currently on location and working on solving the problem. We estimate that this will be resolved within an hour.
Please accept our apologies for any inconvenience this may have caused.
UPDATE: The problem has been identified as being hardware-related. Our technicians are currently making the necessary repairs. We will keep you informed of our progress. As a reminder, this hardware is no longer used on the final release architecture.
UPDATE: We have built a new filer, and VMs are now restarting on it. We are watching your fscks, this seems okay everywhere. An overload of the filer was anticipated for the evening, though has been absorbed nicely. We will soon be migrating this filer to SAS.


