No NFS is involved. All the mounts are ephemeral storage.
Instance types seemed to be isolated to m1.large and c1.xlarge so far. We have the same configuration running on m2.xlarge that we have for some m1.larges and have not seen crashes there (but I wouldn't rule out since we didnt start digging into this issue deeply until recently)
Seen it across multiple AZs in us-east. Amazon checked a few instance ids for us and said they found no hardware issues.
Seen on CPUs
model name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
model name : Intel(R) Xeon(R) CPU E5507 @ 2.27GHz
model name : Intel(R) Xeon(R) CPU E5506 @ 2.13GHz
I only seem to be able to get the Xen version on the 3.0 kernels. Asking Amazon for more info there but on the 3.0 kernels we've seen
No NFS is involved. All the mounts are ephemeral storage.
Instance types seemed to be isolated to m1.large and c1.xlarge so far. We have the same configuration running on m2.xlarge that we have for some m1.larges and have not seen crashes there (but I wouldn't rule out since we didnt start digging into this issue deeply until recently)
Seen it across multiple AZs in us-east. Amazon checked a few instance ids for us and said they found no hardware issues.
Seen on CPUs
model name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
model name : Intel(R) Xeon(R) CPU E5507 @ 2.27GHz
model name : Intel(R) Xeon(R) CPU E5506 @ 2.13GHz
I only seem to be able to get the Xen version on the 3.0 kernels. Asking Amazon for more info there but on the 3.0 kernels we've seen
Xen version: 3.4.3-2.6.18 (preserve-AD)