From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 16:08:26 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9CE079F8 for ; Wed, 19 Nov 2014 16:08:26 +0000 (UTC) Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 40CB8C42 for ; Wed, 19 Nov 2014 16:08:26 +0000 (UTC) Received: by mail-wg0-f41.google.com with SMTP id y19so1166795wgg.28 for ; Wed, 19 Nov 2014 08:08:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=0R5GLoKdkMwyzllFmOLVuCR/CSgUB7Pk2PnfuiKJBe4=; b=EVFNv0Nzew9tYAhZxf5lejeXZwY8CWWTwR4EDRNfrbDysIOIydYWEc4KZa9xY+ve6a JUEyQo4lGaisE3PpSdTtG8h78XuVcB+He2lXF7LPgdfEjyPyrK43VLdpPl5plki5vnwt v4YiTsPsl4f4oWZJrPBlkJJxBvLYyQb8aDQodeXYW5rh3HfZyCVV5pAJP+4ru4D77d0O 5wVDl0ZojpyqXA3tah2/gIzLsDngpZ/onWZax5O0Acr3CXdkV2dqDupnyN5Cgshbrh9J n6xKJB5sxk8HHhUQdXrjVY79Y3d35Yoys7Xj2eviWM8Ipc+H/RNgwpKqJLD98XFB2h13 lxBQ== MIME-Version: 1.0 X-Received: by 10.180.8.34 with SMTP id o2mr6861798wia.23.1416413298952; Wed, 19 Nov 2014 08:08:18 -0800 (PST) Sender: asomers@gmail.com Received: by 10.194.156.229 with HTTP; Wed, 19 Nov 2014 08:08:18 -0800 (PST) In-Reply-To: <166BD891-B686-41F9-A741-9C7E7D989CB8@punkt.de> References: <166BD891-B686-41F9-A741-9C7E7D989CB8@punkt.de> Date: Wed, 19 Nov 2014 09:08:18 -0700 X-Google-Sender-Auth: g4wZRdvTf1u0mQN3phnk8fi_s6M Message-ID: Subject: Re: 10.1 geom "diskid" From: Alan Somers To: "Patrick M. Hausen" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-stable@freebsd.org List" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2014 16:08:26 -0000 On Wed, Nov 19, 2014 at 8:55 AM, Patrick M. Hausen wrote: > Now it's getting decidedly weird: > >> Am 19.11.2014 um 16:40 schrieb Patrick M. Hausen : >> >> Hi, all, >> >> next question, sorry. I just created a fresh 10.1 installation >> with ZFS. With the last reboot after adding dedicated SSD >> based l2arc and zil, the underlying devices are referred to >> by "diskid" instead of the GPT labels I have first been using: >> >> NAME STATE READ WRITE CKSUM >> zroot ONLINE 0 0 0 >> mirror-0 ONLINE 0 0 0 >> gpt/disk0 ONLINE 0 0 0 >> gpt/disk1 ONLINE 0 0 0 >> logs >> diskid/DISK-BTTV334403R7200GGNp2 ONLINE 0 0 0 >> cache >> diskid/DISK-BTTV334403R7200GGNp1 ONLINE 0 0 0 >> >> I can live with that, but I do not understand why the ada2 device >> changed from gpt/* to diskid/* while the others did not? >> >> /dev/gpt entries are not even present for ada2, neither are ada2p? >> >> At least the system could try to be consistent ;-) > > gnop create -S 4096 /dev/diskid/DISK-BTTV334403R7200GGNp3 > zpool create ssd /dev/diskid/DISK-BTTV334403R7200GGNp3.nop > zpool export ssd > gnop destroy /dev/diskid/DISK-BTTV334403R7200GGNp3.nop > zpool import ssd > zpool status Why the gnop acrobatics? It seems that you are trying to force ZFS to treat the disk as though it has 4K sectors. Normally ZFS will use the correct physical sector size as reported by the disk. Have you checked whether it reports it sectorsize correctly? Do "diskinfo -v /devdiskid/DISK-BTTV334403R7200GGNp3" and look for the "stripesize" value. It will probably say either 0 for a 512B drive or 4096 for a 4K drive. If it says 0, and you have accurate information that the true physical sector size is 4K, then we should update the quirk tables in the da and ada drivers. -Alan > > pool: ssd > state: ONLINE > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > ssd ONLINE 0 0 0 > gpt/ssd ONLINE 0 0 0 > > errors: No known data errors > > > WTF? Now it's referring to ada2p3 as gpt/ssd again. Of course the first 2 > partitions are still diskid/DISK-BTTV334403R7200GGNp1 and p2, since > I have not changed anything about the "zroot" pool. > > OK, reboot ... > > zpool status > ... > NAME STATE READ WRITE CKSUM > ssd ONLINE 0 0 0 > diskid/DISK-BTTV334403R7200GGNp3 ONLINE 0 0 0 > > Now all 3 partitions on the SSD are addressed by diskid. The two mirror > vdevs by GPT label, and, needless to say, the two components of my swap > gmirror by legacy devices: > > root@seleniumhub:~ # gmirror status > Name Status Components > mirror/swap COMPLETE ada0p2 (ACTIVE) > ada1p2 (ACTIVE) > > Although I created the mirror using /dev/gpt/swap0 and swap1, of course ;= -) > > > Please do not consider this a major complaint. As long as everything work= s, > I'm perfectly happy. But I'd like to understand what is going on here. > All the recent Ubuntu installs I run refer to disks exclusively by UUID a= nd here > we have three different kinds of devices in a single install. That *might= * > scare away someone some time ... > > > Kind regards > Patrick > -- > punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe > Tel. 0721 9109 0 * Fax 0721 9109 100 > info@punkt.de http://www.punkt.de > Gf: J=C3=BCrgen Egeling AG Mannheim 108285 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"