That's not a crash. That is xfs detecting on disk corruption which likely happened at some time prior. You should unmount and run xfs_repair, possibly with –n first if you would like to do a dry run to see what it might do. If you get fresh corruption after a full repair, then that becomes more interesting. It's possible that you have a problem with the underlying block layer or it's possible that it is an xfs bug - but I think this is not something that we have seen before. Eric > On May 27, 2015, at 6:06 PM, Shrinand Javadekar <shrinand@xxxxxxxxxxxxxx> wrote: > > Hi, > > I am running Openstack Swift in a VM with XFS as the underlying > filesystem. This is generating a metadata heavy workload on XFS. > Essentially, it is creating a new directory and a new file (256KB) in > that directory. This file has extended attributes of size 243 bytes. > > I am seeing the following two crashes of the machine: > > http://pastie.org/pastes/10210974/text?key=xdmfvaocvawnyfmkb06zg > > AND > > http://pastie.org/pastes/10210975/text?key=rkiljsdaucrk7frprzgqq > > I have only seen these when running in a VM. We have run several tests > on physical server but have never seen these problems. > > Are there any known issues with XFS running on VMs? > > Thanks in advance. > -Shri > > _______________________________________________ > xfs mailing list > xfs@xxxxxxxxxxx > http://oss.sgi.com/mailman/listinfo/xfs > _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
