Staff are investigating.
UPDATE
[2014-11-11 23:59:04 | Lars Rohrbach]
Staff continue to look into fileservice issues, but cluster.eecs has been responding normally since about 11:30am.
UPDATE
[2014-11-16 22:52:30 | Lars Rohrbach]
Ultimately at fault was a failed Instructional LDAP server. cluster.eecs currently shares fileserver resources with Instructional fileservice, and the dependence on Instructional LDAP caused cluster.eecs fileservice to become unresponsive.
The configuration of the NetApp fileserver has been updated to completely eliminate dependence on Instructional LDAP service. We are evaluating options to separate Instructional fileservice from cluster.eecs, to better isolate service needs.
Resolved as of 2014-11-11 11:31:00