From owner-freebsd-current@FreeBSD.ORG Fri May 6 09:08:39 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9556106566B; Fri, 6 May 2011 09:08:39 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7079D8FC0C; Fri, 6 May 2011 09:08:39 +0000 (UTC) Received: by qwc9 with SMTP id 9so2640888qwc.13 for ; Fri, 06 May 2011 02:08:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ebTgSJgstI6SyGFSmLbKFiYfivhyHaUSHJR8OfXzF2E=; b=cBuKNLy7p89sqIdQVYxgB51/Dnm5rykDpwxnimIxI79WNBE4IkBaclzTk49+gLDy21 yihUnK7Q/k+GIVKRNXddo0nEy2J20aRoso9BXcdzuwTAg68aRgvaPTV5RuMQRGNCDPUl Nj3cAbFdP5HwAOK0RxQxNbOc1NjiYmoi52P8Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=oE0qIuoXDrpViV5xsJ6lF9nRfbq5UqZmJZdzB3sEp6fnPwCmbpR0UvRL7PX0zrLJlA bzZi/ufUYw3w/6bldE0AZLcVDMfYcxPGtgX06wi6pfvT0EofGy+mv1XDrylXsvA6Lol9 O0TczODIVzrgkyR5dWCXtTtilaNPg5SBn5yYo= MIME-Version: 1.0 Received: by 10.229.112.21 with SMTP id u21mr2335623qcp.62.1304672918573; Fri, 06 May 2011 02:08:38 -0700 (PDT) Received: by 10.229.95.19 with HTTP; Fri, 6 May 2011 02:08:38 -0700 (PDT) In-Reply-To: <4DC3B256.8050800@FreeBSD.org> References: <4DAEAE1B.70207@FreeBSD.org> <4DC3B256.8050800@FreeBSD.org> Date: Fri, 6 May 2011 13:08:38 +0400 Message-ID: From: Sergey Kandaurov To: Alexander Motin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD-Current Subject: Re: Switch from legacy ata(4) to CAM-based ATA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2011 09:08:40 -0000 On 6 May 2011 12:33, Alexander Motin wrote: > Sergey Kandaurov wrote: >> XENHVM uses it's own naming scheme and can name disks as daN or adN, >> depending on virtual block device id. atapci0/ata0/ata1 devices still pr= esent >> there (such as in Bruce Cran's dmesg), but no any disks attached from it= : >> instead, all of them hung from device/vbd/N. >> [In a non-XENHVM mode they are attached from ataN channels, as usual.] >> >> /* >> =A0* Translate Linux major/minor to an appropriate name and unit >> =A0* number. For HVM guests, this allows us to use the same drive names >> =A0* with blkfront as the emulated drives, easing transition slightly. >> =A0*/ >> >> xenbusb_front0: on xenstore0 >> xenbusb_back0: on xenstore0 >> xctrl0: on xenstore0 >> xbd0: 17000MB at device/vbd/768 on xenbusb_front0 >> xbd0: attaching as ad0 >> GEOM: ad0s1: geometry does not match label (16h,63s !=3D 255h,63s). >> xbd1: 3812MB at device/vbd/2048 on xenbusb_front0 >> xbd1: attaching as da0 >> xbd2: 114439MB at device/vbd/2064 on xenbusb_fron= t0 >> xbd2: attaching as da1 > > OK, interesting question. I have built amd64 XENHVM kernel and booted it > under Xen 3.2. As result I've got double set of devices, via both > atapci0/ata0 and via blkfront: > > ada0 at ata0 bus 0 scbus0 target 0 lun 0 > ada0: ATA-7 device > ada0: Serial Number QM00001 > ada0: 16.700MB/s transfers (WDMA2, PIO 8192bytes) > ada0: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) > ada0: Previously was known as ad0 > ada1 at ata0 bus 0 scbus0 target 1 lun 0 > ada1: ATA-7 device > ada1: Serial Number QM00002 > ada1: 16.700MB/s transfers (WDMA2, PIO 8192bytes) > ada1: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) > ada1: Previously was known as ad1 > xbd0: 476940MB at device/vbd/768 on xenbusb_front0 > xbd0: attaching as ad0 > xbd1: 476940MB at device/vbd/832 on xenbusb_front0 > xbd1: attaching as ad1 > Both of them were exported to GEOM. Extra set of adX devices caused > error messages. What am I doing wrong and why have I got those > duplicates? Was I required to remove non-PV drivers from my kernel? Doh. This corresponds to errors omitted unintentionally in my previous mail= . This is right after "xbd2: attaching as da1": da0 at sym0 bus 0 scbus2 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 3.300MB/s transfers da0: Command Queueing enabled da0: 3812MB (7807527 512 byte sectors: 255H 63S/T 485C) can't re-use a leaf (led)! g_dev_taste: make_dev_p() failed (gp->name=3Dda0, error=3D17) da1 at sym0 bus 0 scbus2 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 3.300MB/s transfers da1: Command Queueing enabled da1: 114439MB (234372222 512 byte sectors: 255H 63S/T 14588C) can't re-use a leaf (led)! g_dev_taste: make_dev_p() failed (gp->name=3Dda1, error=3D17) No ada devices detected though. --=20 wbr, pluknet