There was a short thread some time ago with a similar symptom:
Were you trying to resize a share or during which action did this error occur?