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-api

Re: [Xen-API] XCP 1.0-beta: md on dom0 kernel causes kernel oops

To: Simon Rowe <simon.rowe@xxxxxxxxxxxxx>
Subject: Re: [Xen-API] XCP 1.0-beta: md on dom0 kernel causes kernel oops
From: Tomoe Sugihara <sugihara@xxxxxxxxxxxxx>
Date: Thu, 02 Dec 2010 08:03:48 +0900
Cc: Jonathan Ludlam <Jonathan.Ludlam@xxxxxxxxxxxxx>, "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 01 Dec 2010 15:04:34 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <201012011652.58326.simon.rowe@xxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <4CF35437.8000500@xxxxxxxxxxxxx> <3183A28E-A8EA-48B3-B43D-A3B5B2B73471@xxxxxxxxxxxxx> <201012011652.58326.simon.rowe@xxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Lightning/1.0b1 Thunderbird/3.0.10
Hi guys,

On 12/02/2010 01:52 AM, Simon Rowe wrote:
On Wednesday 01 Dec 2010 16:49:42 Jonathan Ludlam wrote:

Hum. I'm not too sure myself about kernel issues - Simon Rowe (cc'd) may be
able to help?

Can you describe your setup a little more? What devices are under md?


Thanks for following up on this.
I tried the following two and both ended up with Oops.

1. just two regular HDDs --- /dev/sdc and /dev/sde or whatever.

   Here's how I reproduced just now.Very soon after dd, kernel panics.

$ mdadm --create /dev/md0 --level=mirror --raid-devices=2 /dev/sdc /dev/sde mdadm: /dev/sdc appears to be part of a raid array:
        level=raid1 devices=2 ctime=Mon Nov 29 15:52:53 2010
    mdadm: /dev/sde appears to be part of a raid array:
        level=raid1 devices=2 ctime=Mon Nov 29 09:34:34 2010
    Continue creating array? y
    mdadm: array /dev/md0 started.
    $ dd if=/dev/zero of=/dev/md0 bs=1M

2. dm linear devices which are on top of iscsi

  mdadm --create /dev/mirror/000008bc --auto=md --bitmap=internal --metadata=0 
--run --bitmap-chunk=65536 --delay=5   --level=1 --assume-clean 
--raid-devices=3 /dev/mapper/00000001-00000003 /dev/mapper/00000002-000002d7 
/dev/mapper/00000003-0000050a

   Interestingly, his doesn't cause kernel panic; similar stack trace shows up 
in dmsg and mdadm stalls.


Best,
Tomoe

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api