Sandeep Kumbhar
Thu, 24 Dec 2009 20:10:55 -0800
Hi All
I have a serious issue in one of my project.I am using
Supermicro Server (Custom make) with the below config
CPU : Intel Xeon Quad Core 2.0 Ghz RAM : 32 GB HDD : 6 TB --> configured under RAID 5 RAID bus controller: 3ware Inc 9650SE SATA-II RAID PCIe (rev 01) I have installed Xen Server 5.5.0 on it.I am creating two VM each on it with the below config VCPU: 3 RAM: 15 GB HDD: 2 TB When I start installation on both the VM simultaneouly it works fine , but when I start the untar process of the backup I have taken of original server on both the VM the filesystem goes into *read-only mode of one of the VM *and the other work well. I get the below error on the VM Console as shown below : end_request: I/O error, dev xvda, sector 2899857350 Buffer I/O error on device xvda5, logical block 335832334 lost page write due to I/O error on xvda5 Buffer I/O error on device xvda5, logical block 335832335 lost page write due to I/O error on xvda5 Buffer I/O error on device xvda5, logical block 335832336 lost page write due to I/O error on xvda5 Buffer I/O error on device xvda5, logical block 335832337 lost page write due to I/O error on xvda5 Buffer I/O error on device xvda5, logical block 335832338 lost page write due to I/O error on xvda5 Buffer I/O error on device xvda5, logical block 335832339 lost page write due to I/O error on xvda5 Buffer I/O error on device xvda5, logical block 335832340 lost page write due to I/O error on xvda5 Buffer I/O error on device xvda5, logical block 335832341 lost page write due to I/O error on xvda5 Buffer I/O error on device xvda5, logical block 335832342 lost page write due to I/O error on xvda5 Buffer I/O error on device xvda5, logical block 335832343 lost page write due to I/O error on xvda5 Aborting journal on device xvda5. ext3_abort called. EXT3-fs error (device xvda5): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only EXT3-fs error (device xvda5) in ext3_ordered_writepage: IO failure __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_frozen_data __journal_remove_journal_head: freeing b_frozen_data __journal_remove_journal_head: freeing b_frozen_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_frozen_data __journal_remove_journal_head: freeing b_frozen_data __journal_remove_journal_head: freeing b_frozen_data __journal_remove_journal_head: freeing b_frozen_data __journal_remove_journal_head: freeing b_committed_data What is the problem? and what is causing this ? I have crawled through the internet but no pointers.The HDD used are Server HDD's . I have tried upgrading 3ware Raid Controller drivers then too then I am facing the problem. If any pointer let me know ? Thanks & Regards Sandeep A. Kumbhar