From owner-freebsd-current@FreeBSD.ORG Fri May 6 09:17:13 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 45D7E106564A for ; Fri, 6 May 2011 09:17:13 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id C00358FC18 for ; Fri, 6 May 2011 09:17:12 +0000 (UTC) Received: by fxm11 with SMTP id 11so2932078fxm.13 for ; Fri, 06 May 2011 02:17:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=ZIgtE3bAfsaE/BZeTssiMzIa6qIiFErXT4BasR1FAAA=; b=MkOkakORQ/q7Pns/NLyUSnKVwx8PXZYWU6niXb4x9tMVexf9RZCOMMxZyJIE/V6kcU RlLoOzz0S2TNsZxo+yYPPTvrfYubvku0I29DMcjV52HvqvfDPiNLC75S2Z4DZGv3IluO EJHSK5No3D3JLZfM9gVqyfExzoY9E9FCuSLgE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=P2SWK36vY75K6xkiiLBdLc7Wa2h51XMGl/rISbhgxr2is4aFTPC9xc9SiMZGZO5yTZ 38e/TFEVWeIZ914qb5wPvqMihsWKWey0CJuf7pivC7UgQcX92wCJ/3IcZvcH6tXThjWa U61M1d52tpmngpCN6evHNrM/pQVmdlAxD90Rg= Received: by 10.223.1.201 with SMTP id 9mr2504647fag.91.1304673431693; Fri, 06 May 2011 02:17:11 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 9sm1019497fat.15.2011.05.06.02.17.10 (version=SSLv3 cipher=OTHER); Fri, 06 May 2011 02:17:11 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DC3BC76.4000102@FreeBSD.org> Date: Fri, 06 May 2011 12:16:38 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Sergey Kandaurov References: <4DAEAE1B.70207@FreeBSD.org> <4DC3B256.8050800@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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:17:13 -0000 Sergey Kandaurov wrote: > 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 present >>> 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.] >>> >>> /* >>> * Translate Linux major/minor to an appropriate name and unit >>> * number. For HVM guests, this allows us to use the same drive names >>> * with blkfront as the emulated drives, easing transition slightly. >>> */ >>> >>> 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 != 255h,63s). >>> xbd1: 3812MB at device/vbd/2048 on xenbusb_front0 >>> xbd1: attaching as da0 >>> xbd2: 114439MB at device/vbd/2064 on xenbusb_front0 >>> 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=da0, error=17) > 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=da1, error=17) > > No ada devices detected though. But you have duplicate daX here. It is just the same, except that you have different Xen configuration -- disks configured as SCSI instead of ATA. So the question is the same: how this supposed to work? To me, that double detection problem seems much more significant then names change. -- Alexander Motin