Read-only filesystems on Birmingham instances

FINAL UPDATE 2030 9th May 2017

This problem should now be fixed and we’ve done our best to ensure all instances are running again.

I’m afraid that you’ll have to restart any tasks that were running when the filesystem went read-only at about 12 pm today.

Apologies for the unplanned service disruption.


We’ve had a small problem with the underlying storage at Birmingham today which we’re working on resolving.

This post will be updated with more information ASAP.


EDIT 1654 9th May 2017

We’re going to have to reboot some instances, apologies again for the inconvenience.


EDITED 1419 9th May 2017 - Original post below

We’ve had a small problem with the underlying storage at Birmingham today which we’ve now resolved.

If you find that your instance filesystem has become read-only, please hard-reboot your instance from the https://bryn.climb.ac.uk1 control panel to fix it.