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

[Chao-Rui Chang <ppc52776@xxxxxxxxx>]

Pasi,

I have tried xen-4.0, 4.0.1-rc1,rc2, latest hg version

xen-4.0: failed at boot time
xen-4.0.1*: failed after several hours

I will try 4.0.1-rc4 now.

Thanks.

2010/7/21 Pasi KÃrkkÃinen <pasik@xxxxxx>

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