Created attachment 611679 [details] Kernel panic screenshot Description of problem: In RHEVM, we added a disk and increased memory of an existing VM. When the VM was started again, we saw a kernel panic. Version-Release number of selected component (if applicable): glusterfs-3.3.0rhsvirt1-2.el6_2.x86_64 How reproducible: We don't have steps to reproduce Steps to Reproduce: 1. Create a 2x2 Distributed-Replicated volume 2. Install the VM using RHS-2.0-20120503.1-RHS-x86_64-DVD1.iso 3. Shutdown the VM, add memory and disk 4. Start the VM Actual results: Kernel panic Expected results: Shouldn't panic Additional info:
Anush, this doesn't look like a gluster issue... Can you confirm the behavior on backend FS itself?
Amar, how to try it directly on the backend FS? Should we try it on a VM hosted on a NFS export storage domain?
Anush, yes, you can try it on NFS data store, also you can use backend FS directly using posixfs to mount a XFS volume (on /dev/sd*N)... But for verification, NFS data store is good enough. Also as Yaniv mentioned in the call, it could have got fixed with later RHEV-H versions, as there was some similar bug there.
Unable to reproduce this issue with the latest build, glusterfs-3.3.0rhsvirt1-8.el6rhs.x86_64