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: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-users] xen-4 + megasas(DELL 6i RAID) = Reject I/O to offline device
From: Chao-Rui Chang <ppc52776@xxxxxxxxx>
Date: Wed, 21 Jul 2010 02:05:27 +0800
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 20 Jul 2010 11:07:57 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=rHBCHX6+M2UZeBJP7FXXVmr0jnurPKHt0z3gCg32QLs=; b=hYZ5EkY9+Lg7NgbbFKLFbBjYw2iuZ2oZLxlc3jP64uqUTTMjzoiDhColMKngW48cHh ZrqZ21N/2WDMpwvL1Kiif9KLJtU0oF2H2Wjft0sfGd8s7xhkryO+vayRhE9YpIpzCT0Z w6vm9XS1sXkNJkI5hqy5xduR0Ghmuws+HFMFw=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=dFh9K/7n0LRIcGQYLTTvKHDqkGTAefYYX13s66G6JVgUA79qKZ0Pf3ryqAd2AZVZtD 91pOj0WNxDn+VqHaiZCTjQRfJP+aVPs/fxuxyNxEFKAH3I0f43T9++Qki9dikoMGXhcE r+diTI4dGHH2gGnsbO55aXvIX3LiIpPGSrhTc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100720171712.GJ17817@xxxxxxxxxxx>
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> <20100720122643.GC17817@xxxxxxxxxxx> <AANLkTikmlSfFW8IXG0U5kukOtajc9eW7oqbS9aagw7tT@xxxxxxxxxxxxxx> <20100720171712.GJ17817@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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
>    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
<Prev in Thread] Current Thread [Next in Thread>