WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

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

To: Chao-Rui Chang <ppc52776@xxxxxxxxx>
Subject: 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 15:26:43 +0300
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 20 Jul 2010 05:28:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTilcMUD3xIdqA9MnR0xp23iEAd-iScowjXLuQ21Y@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTilcMUD3xIdqA9MnR0xp23iEAd-iScowjXLuQ21Y@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
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.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]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. http://2.6.32.16/
>    2. http://2.6.32.16/

> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>