Date: Wed, 16 Nov 2016 11:44:32 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> To: FreeBSD Xen <freebsd-xen@freebsd.org> Subject: Maximum number of virtual disks and inconsistent naming of device files Message-ID: <alpine.BSF.2.20.1611161119500.32949@mail.fig.ol.no>
next in thread | raw e-mail | index | archive | help
Hi, I'm running XenServer 7.0.0. I tried to add the fourth, the fifth, and the sixth drive to a FreeBSD VM running stable/11 r308642, with the (almost unrelated) patch from r308126 applied. The problem is that only the first three drives gets attached, the last three drives are detected, but not acted upon: xbd0: 12288MB <Virtual Block Device> at device/vbd/832 on xenbusb_front0 xbd0: attaching as ada1 xbd0: features: write_barrier xbd0: synchronize cache commands enabled. xbd1: 12288MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0 xbd1: attaching as ada0 xbd1: features: write_barrier xbd1: synchronize cache commands enabled. xbd2: 12288MB <Virtual Block Device> at device/vbd/5632 on xenbusb_front0 xbd2: attaching as ada2 xbd2: features: write_barrier xbd2: synchronize cache commands enabled. xbd4: 2048MB <Virtual Block Device> at device/vbd/51776 on xenbusb_front0 xbd4: features: write_barrier xbd4: synchronize cache commands enabled. xbd5: 2048MB <Virtual Block Device> at device/vbd/51792 on xenbusb_front0 xbd5: features: write_barrier xbd5: synchronize cache commands enabled. xbd6: 2048MB <Virtual Block Device> at device/vbd/51808 on xenbusb_front0 xbd6: features: write_barrier xbd6: synchronize cache commands enabled. Can we get the three remaining drives attached as ada3, ada4, and ada5? Also, why is the naming of the device files inconsistent with the drive order? xbd0 => ada1 xbd1 => ada0 xbd2 => ada2 <= This one's consistent, but that's probably by accident. Are the drives 0, 1, 2, 4, 5, and 6, as shown in XenCenter, really xbd0, xbd1, xbd2, xbd4, xbd5, xbd6? Wouldn't this mapping make more sense: xbd0 => ada0 xbd1 => ada1 xbd2 => ada2 xbd4 => ada3 xbd5 => ada4 xbd6 => ada5 -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-xen@freebsd.org Wed Nov 16 11:06:10 2016 Return-Path: <owner-freebsd-xen@freebsd.org> Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BBC65C44400 for <freebsd-xen@mailman.ysv.freebsd.org>; Wed, 16 Nov 2016 11:06:10 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6488D12D6 for <freebsd-xen@freebsd.org>; Wed, 16 Nov 2016 11:06:10 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id uAGB663b033321 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <freebsd-xen@freebsd.org>; Wed, 16 Nov 2016 12:06:06 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id uAGB66tD033318 for <freebsd-xen@freebsd.org>; Wed, 16 Nov 2016 12:06:06 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Wed, 16 Nov 2016 12:06:06 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> Sender: Trond.Endrestol@fagskolen.gjovik.no To: FreeBSD Xen <freebsd-xen@freebsd.org> Subject: Re: Maximum number of virtual disks and inconsistent naming of device files In-Reply-To: <alpine.BSF.2.20.1611161119500.32949@mail.fig.ol.no> Message-ID: <alpine.BSF.2.20.1611161203160.32949@mail.fig.ol.no> References: <alpine.BSF.2.20.1611161119500.32949@mail.fig.ol.no> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage <freebsd-xen.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-xen>, <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>; List-Post: <mailto:freebsd-xen@freebsd.org> List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-xen>, <mailto:freebsd-xen-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 16 Nov 2016 11:06:10 -0000 On Wed, 16 Nov 2016 11:44+0100, Trond Endrestøl wrote: > Hi, > > I'm running XenServer 7.0.0. I tried to add the fourth, the fifth, and > the sixth drive to a FreeBSD VM running stable/11 r308642, with the > (almost unrelated) patch from r308126 applied. > > The problem is that only the first three drives gets attached, the > last three drives are detected, but not acted upon: > > xbd0: 12288MB <Virtual Block Device> at device/vbd/832 on xenbusb_front0 > xbd0: attaching as ada1 > xbd0: features: write_barrier > xbd0: synchronize cache commands enabled. > xbd1: 12288MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0 > xbd1: attaching as ada0 > xbd1: features: write_barrier > xbd1: synchronize cache commands enabled. > xbd2: 12288MB <Virtual Block Device> at device/vbd/5632 on xenbusb_front0 > xbd2: attaching as ada2 > xbd2: features: write_barrier > xbd2: synchronize cache commands enabled. > xbd4: 2048MB <Virtual Block Device> at device/vbd/51776 on xenbusb_front0 > xbd4: features: write_barrier > xbd4: synchronize cache commands enabled. > xbd5: 2048MB <Virtual Block Device> at device/vbd/51792 on xenbusb_front0 > xbd5: features: write_barrier > xbd5: synchronize cache commands enabled. > xbd6: 2048MB <Virtual Block Device> at device/vbd/51808 on xenbusb_front0 > xbd6: features: write_barrier > xbd6: synchronize cache commands enabled. > > Can we get the three remaining drives attached as ada3, ada4, and > ada5? I discovered the device files xbd{4,5,6} and created a zpool using these drives, so we can check this item off the list. > Also, why is the naming of the device files inconsistent with the > drive order? > > xbd0 => ada1 > xbd1 => ada0 > xbd2 => ada2 <= This one's consistent, but that's probably by accident. Consistency would be nice. > Are the drives 0, 1, 2, 4, 5, and 6, as shown in XenCenter, really > xbd0, xbd1, xbd2, xbd4, xbd5, xbd6? I guess this is true. > Wouldn't this mapping make more sense: > > xbd0 => ada0 > xbd1 => ada1 > xbd2 => ada2 > xbd4 => ada3 > xbd5 => ada4 > xbd6 => ada5 This doesn't apply. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-xen@freebsd.org Wed Nov 16 14:11:02 2016 Return-Path: <owner-freebsd-xen@freebsd.org> Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12E2BC4545A for <freebsd-xen@mailman.ysv.freebsd.org>; Wed, 16 Nov 2016 14:11:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 02B3633A for <freebsd-xen@FreeBSD.org>; Wed, 16 Nov 2016 14:11:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uAGEB1jr048805 for <freebsd-xen@FreeBSD.org>; Wed, 16 Nov 2016 14:11:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 212681] I/O is slow for FreeBSD DOMu on XenServer Date: Wed, 16 Nov 2016 14:11:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rainer@ultra-secure.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-212681-23905-glGcPInqJg@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-212681-23905@https.bugs.freebsd.org/bugzilla/> References: <bug-212681-23905@https.bugs.freebsd.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage <freebsd-xen.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-xen>, <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>; List-Post: <mailto:freebsd-xen@freebsd.org> List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-xen>, <mailto:freebsd-xen-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 16 Nov 2016 14:11:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212681 --- Comment #19 from rainer@ultra-secure.de --- Updating to ScaleIO 2.0.3 (and all the latest Hotfixes of XenServer 6.5) doesn't make a difference. How would one debug this problem? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1611161119500.32949>