Instance - fsck

asked 2015-04-28 15:07:33 -0600

stacksam gravatar image


I've Havana Openstack setup using KVM/libvirt based instances. I've observed that when an hypervisor goes down abruptly for an hardware issue. After bringing up instances running RHEL 5, they end up read-only filesystem after boot up ( with clean filesystem check during boot up. The instances use the storage on the hypervisor ( raid controller and sata drives ). Sometimes during boot up the fsck is enforced to run manually.

I understand why the fsck is required but the when the fsck was clean on the hypervisor, shouldn't the instances devices get the clean view of the filesystem?

If the clean view is not there, why wouldn't instances enforced fsck during bootup instead of saying it's clean and reports that a filesystem is read only after boot up?

To me it seems the proper view of the hypervisor filesystem view doesn't get propagated to instances.

Any idea and comments?

edit retag flag offensive close merge delete


Am not clear in my question or no one out there went through this problem?

stacksam gravatar imagestacksam ( 2015-04-29 17:29:28 -0600 )edit