Xen project Mailing List

Re: [Xen-users] xen-4 + megasas(DELL 6i RAID) = Reject I/O to offline device

From: Pasi Kärkkäinen <pasik@xxxxxx>

Date: Tue, 20 Jul 2010 20:17:12 +0300

Delivery-date: Tue, 20 Jul 2010 10:18:55 -0700

List-id: Xen user discussion <xen-users.lists.xensource.com>

On Wed, Jul 21, 2010 at 01:11:59AM +0800, Chao-Rui Chang wrote: > Pasi, > > Yes, it works fine without xen. > Ok. Did you try Xen 4.0.1-rc4 ? -- Pasi > 2010/7/20 Pasi KÃârkkÃâinen <[1]pasik@xxxxxx> > > On Tue, Jul 20, 2010 at 03:27:19PM +0800, Chao-Rui Chang wrote: > > Ã Ã Dear folks, > > > > Ã Ã I have problem with xen-4 + megasas driver (dell raid card 6i). > > Ã Ã The raid controller goes offline randomly. > > > > Ã Ã This may be the xen hypervisor problem. > > > > I don't think it's a problem with Xen hypervisor. > It's more probably a problem with the dom0 kernel. > > Does the same kernel work OK when it's booted on native baremetal > (without Xen) ? > > -- Pasi > > Ã Ã The following is the log message from xen 4.0 and 4.1-unstable: > > > > Ã Ã xen 4.1-unstable + kernel [1][2]2.6.32.16: > > Ã Ã Ã* Ã* Ã* Ã* Ã* Ã ->System can boot, but megasas fail after about > 3-4 hours > > Ã Ã Ã* Ã* Ã* Ã* Ã megasas: [ 0]waiting for 25 commands to complete > > Ã Ã Ã* Ã* Ã* Ã* Ã megasas: [ 5]waiting for 25 commands to complete > > Ã Ã Ã* Ã* Ã* Ã* Ã megasas: [10]waiting for 25 commands to complete > > Ã Ã Ã* Ã* Ã* Ã* Ã megasas: [15]waiting for 25 commands to complete > > Ã Ã Ã* Ã* Ã* Ã* Ã megasas: [20]waiting for 25 commands to complete > > Ã Ã Ã* Ã* Ã* Ã* Ã megasas: [25]waiting for 25 commands to complete > > Ã Ã Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* > Ã ... > > Ã Ã Ã* Ã* Ã* Ã* Ã megasas: cannot recover from previous reset > failures > > Ã Ã Ã* Ã* Ã* Ã* Ã end_request: I/O error, dev sda, sector 46755821 > > Ã Ã Ã* Ã* Ã* Ã* Ã Buffer I/O error on device dm-0, logical block > 5818372 > > Ã Ã Ã* Ã* Ã* Ã* Ã lost page write due to I/O error on dm-0 > > Ã Ã Ã* Ã* Ã* Ã* Ã Buffer I/O error on device dm-0, logical block > 5818373 > > Ã Ã Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã ... > > Ã Ã Ã* Ã* Ã* Ã* Ã end_request: I/O error, dev sda, sector 7024621 > > Ã Ã Ã* Ã* Ã* Ã* Ã Aborting journal on device dm-0. > > Ã Ã Ã* Ã* Ã* Ã* Ã end_request: I/O error, dev sda, sector 7024653 > > Ã Ã Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã ... > > Ã Ã Ã* Ã* Ã* Ã* Ã ext4-fs error (device dm-0) in ext4_dirty_inode: > Journal has > > Ã Ã aborted > > Ã Ã Ã* Ã* Ã* Ã* Ã sd 0:2:0:0: rejecting I/O to offline device > > Ã Ã Ã* Ã* Ã* Ã* Ã ext4_abort called. > > Ã Ã Ã* Ã* Ã* Ã* Ã ext4-fs error (device dm-0): ext4_journal_start_sb: > Detected > > Ã Ã aborted journal > > Ã Ã Ã* Ã* Ã* Ã* Ã Remounting filesystem read-only > > Ã Ã Ã* Ã* Ã* Ã* Ã end_request: I/O error, dev sda, sector 7024861 > > Ã Ã Ã* Ã* Ã* Ã* Ã end_request: I/O error, dev sda, sector 7024893 > > Ã Ã Ã* Ã* Ã* Ã* Ã ext4-fs error (device dm-0) in > ext4_reserve_inode_write: Journal > > Ã Ã has aborted > > Ã Ã Ã* Ã* Ã* Ã* Ã ext4-fs error (device dm-0) in > ext4_reserve_inode_write: Journal > > Ã Ã has aborted > > Ã Ã Ã* Ã* Ã* Ã* Ã end_request: I/O error, dev sda, sector 7024965 > > Ã Ã Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã ... > > Ã Ã Ã* Ã* Ã* Ã* Ã Buffer I/O error on device dm-0, logical block 1 > > Ã Ã Ã* Ã* Ã* Ã* Ã lost page write due to I/O error on dm-0 > > Ã Ã Ã* Ã* Ã* Ã* Ã sd 0:2:0:0: rejecting I/O to offline device > > Ã Ã Ã* Ã* Ã* Ã* Ã sd 0:2:0:0: rejecting I/O to offline device > > Ã Ã Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã ... > > > > Ã Ã xen 4.0-stable + kernel [2][3]2.6.32.16: > > Ã Ã Ã* Ã* Ã* Ã* Ã* Ã ->System can not boot, megasas fail at boot time > > Ã Ã xen: registering gsi 33 triggering 0 polarity 1 > > Ã Ã xen: --> irq=33 > > Ã Ã megaraid_sas 0000:03:00.0: PCI INT A -> GSI 33 (level, low) -> > IRQ 33 > > Ã Ã megaraid_sas 0000:03:00.0: setting latency timer to 64 > > Ã Ã megasas: FW now in Ready state > > Ã Ã scsi0 : LSI SAS based MegaRAID driver > > Ã Ã scsi 0:0:0:0: Direct-AccessÃ* Ã* Ã* Ã* Ã ATAÃ* Ã* Ã* Ã* Ã* Ã WDC > WD1002FBYS-1 0C10 > > Ã Ã PQ: 0 ANSI: 5 > > Ã Ã scsi 0:0:1:0: Direct-AccessÃ* Ã* Ã* Ã* Ã ATAÃ* Ã* Ã* Ã* Ã* Ã WDC > WD1002FBYS-1 0C10 > > Ã Ã PQ: 0 ANSI: 5 > > Ã Ã scsi 0:0:2:0: Direct-AccessÃ* Ã* Ã* Ã* Ã ATAÃ* Ã* Ã* Ã* Ã* Ã WDC > WD1002FBYS-1 0C10 > > Ã Ã PQ: 0 ANSI: 5 > > Ã Ã scsi 0:0:32:0: EnclosureÃ* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã DPÃ* Ã* Ã* Ã* > Ã* Ã* > > Ã Ã BACKPLANEÃ* Ã* Ã* Ã* Ã* Ã* Ã* Ã 1.07 PQ: 0 ANSI: 5 > > Ã Ã scsi 0:2:0:0: Direct-AccessÃ* Ã* Ã* Ã* Ã DELLÃ* Ã* Ã* Ã* Ã PERC > 6/iÃ* Ã* Ã* Ã* Ã* Ã* Ã* Ã* > > Ã Ã 1.22 PQ: 0 ANSI: 5 > > Ã Ã megasas: [ 0]waiting for 25 commands to complete > > Ã Ã megasas: [ 5]waiting for 25 commands to complete > > Ã Ã Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã .... > > > > Ã Ã any idea about this problem? > > > > Ã Ã Thanks. > > Ã Ã ----------------------------------------------------- > > Ã Ã Best regards, > > Ã Ã Chao-Rui > > > > References > > > > Ã Ã Visible links > > Ã Ã 1. [4]http://2.6.32.16/ > > Ã Ã 2. [5]http://2.6.32.16/ > > > _______________________________________________ > > Xen-users mailing list > > [6]Xen-users@xxxxxxxxxxxxxxxxxxx > > [7]http://lists.xensource.com/xen-users > > References > > Visible links > 1. mailto:pasik@xxxxxx > 2. http://2.6.32.16/ > 3. http://2.6.32.16/ > 4. http://2.6.32.16/ > 5. http://2.6.32.16/ > 6. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx > 7. http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.