There's a customer case attached to this BZ, it should not be in low severity. Raised it a bit as well as set priority to it. Moved to ASSIGNED assuming Brad is handling it - please fix if I'm wrong here.
The ceph-osd crash looks to be a side-effect of the issues occurring on the system at the time. The kernel on this machine was effectively hung at the time leading to significant IO stalls. This was a highly unstable and unpredictable environment in which no application could realistically be expected to continue functioning (this is reinforced by the fact that systemd was seen to be crashing at the same time). The osd process appears to be in pthread code which is some of the most highly used and bullet-proof code out there so this reinforces that the environment was highly unstable. There is no additional data such as a coredump which would assist us in further pinpointing the exact nature of the issue but I don't believe any further investigation of this crash is a good use of engineering's time since no non-trivial application should be expected to continue functioning in such circumstances (not to mention we would not support such a configuration of all storage on a single vSphere datastore). If no one objects I propose closing this Bugzilla NOTABUG.