From owner-freebsd-geom@FreeBSD.ORG Sun Mar 8 20:51:25 2009 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9F19106564A for ; Sun, 8 Mar 2009 20:51:25 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 8F6E58FC08 for ; Sun, 8 Mar 2009 20:51:25 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 05ABA7309E; Sun, 8 Mar 2009 21:38:12 +0100 (CET) Date: Sun, 8 Mar 2009 21:38:12 +0100 From: Luigi Rizzo To: Ivan Voras Message-ID: <20090308203811.GA4042@onelab2.iet.unipi.it> References: <20090308005515.GA68934@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, freebsd-geom@freebsd.org Subject: Re: updated geom_sched code X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2009 20:51:26 -0000 On Sun, Mar 08, 2009 at 07:38:30PM +0100, Ivan Voras wrote: > Luigi Rizzo wrote: ... > > Apart from that (which needs to be fixed by adding a field to the > > struct bio), we believe the code to be quite stable now, so future ... > Hi, > > Do you have some documentation about the long-term plans? You will have > to add an additional field to bio, of course, but there is one more > thing: the schedulers will have to be integrated into the GEOM in an > "invisible" way. I.e. instead of /dev/ad0-sched-s1f the users should see > only /dev/ad0 like they're used to, and get the schedulers by default. > Otherwise, your work will not get much use. well, if one is comfortable with the schedulers he can just put the right names in /etc/fstab. I think the usefulness of 'invisible' classes is more when adding or removing geom classes on the fly, but perhaps this requires support in the geom nodes themselves. In any case I was hoping to discuss this issue later, either at bsdcan or in the mailing list, once I understand the implications a bit more. cheers luigi From owner-freebsd-geom@FreeBSD.ORG Mon Mar 9 17:15:04 2009 Return-Path: Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76CE610656BC for ; Mon, 9 Mar 2009 17:15:04 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6342F8FC16 for ; Mon, 9 Mar 2009 17:15:04 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n29HF4Yb045242 for ; Mon, 9 Mar 2009 17:15:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n29HF3t0045237 for freebsd-geom@FreeBSD.org; Mon, 9 Mar 2009 17:15:03 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 9 Mar 2009 17:15:03 GMT Message-Id: <200903091715.n29HF3t0045237@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-geom@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2009 17:15:04 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/132273 geom [glabel] [patch] failing on journaled partition o kern/132242 geom [gmirror] gmirror.ko fails to fully initialize o kern/131575 geom [geom_label] [msdosfs] [umass] Immediate crash after p o kern/131353 geom [geom] gjournal(8) kernel lock o kern/131037 geom [geli] Unable to create disklabel on .eli-Device o kern/130528 geom gjournal fsck during boot o kern/129674 geom [geom] gjournal root did not mount on boot o kern/129645 geom gjournal(8): GEOM_JOURNAL causes system to fail to boo o kern/129245 geom [geom] gcache is more suitable for suffix based provid o bin/128398 geom [patch] glabel(8): teach geom_label to recognise gpt l f kern/128276 geom [gmirror] machine lock up when gmirror module is used o kern/126902 geom [geom] [geom_label] Kernel panic during install boot o kern/124973 geom [gjournal] [patch] boot order affects geom_journal con o kern/124969 geom gvinum(8): gvinum raid5 plex does not detect missing s o kern/124294 geom [geom] gmirror(8) have inappropriate logic when workin o kern/124130 geom [gmirror] [usb] gmirror fails to start usb devices tha o kern/123962 geom [panic] [gjournal] gjournal (455Gb data, 8Gb journal), o kern/123630 geom [patch] [gmirror] gmirror doesnt allow the original dr o kern/123122 geom [geom] GEOM / gjournal kernel lock f kern/122415 geom [geom] UFS labels are being constantly created and rem o kern/122067 geom [geom] [panic] Geom crashed during boot o kern/121559 geom [patch] [geom] geom label class allows to create inacc o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/120231 geom [geom] GEOM_CONCAT error adding second drive o kern/120044 geom [msdosfs] [geom] incorrect MSDOSFS label fries adminis o kern/120021 geom [geom] [panic] net-p2p/qbittorrent crashes system when o kern/119743 geom [geom] geom label for cds is keeped after dismount and f kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/114532 geom [geom] GEOM_MIRROR shows up in kldstat even if compile o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113419 geom [geom] geom fox multipathing not failing back p bin/110705 geom gmirror(8) control utility does not exit with correct o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o bin/90093 geom fdisk(8) incapable of altering in-core geometry a kern/89660 geom [vinum] [patch] [panic] due to g_malloc returning null o kern/89546 geom [geom] GEOM error s kern/89102 geom [geom] [panic] panic when forced unmount FS from unplu o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo o kern/84556 geom [geom] [panic] GBDE-encrypted swap causes panic at shu o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/79035 geom [vinum] gvinum unable to create a striped set of mirro o bin/78131 geom gbde(8) "destroy" not working. s kern/73177 geom kldload geom_* causes panic due to memory exhaustion 48 problems total. From owner-freebsd-geom@FreeBSD.ORG Tue Mar 10 16:00:14 2009 Return-Path: Delivered-To: freebsd-geom@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4034D1065672 for ; Tue, 10 Mar 2009 16:00:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 141D58FC19 for ; Tue, 10 Mar 2009 16:00:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2AG0DQP046259 for ; Tue, 10 Mar 2009 16:00:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2AG0DPr046258; Tue, 10 Mar 2009 16:00:13 GMT (envelope-from gnats) Date: Tue, 10 Mar 2009 16:00:13 GMT Message-Id: <200903101600.n2AG0DPr046258@freefall.freebsd.org> To: freebsd-geom@FreeBSD.org From: Guido van Rooij Cc: Subject: Re: kern/113957: [gmirror] gmirror is intermittently reporting a degraded mirror array upon reboot. X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Guido van Rooij List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2009 16:00:14 -0000 The following reply was made to PR kern/113957; it has been noted by GNATS. From: Guido van Rooij To: bug-followup@FreeBSD.org, ayochum@pair.com Cc: Subject: Re: kern/113957: [gmirror] gmirror is intermittently reporting a degraded mirror array upon reboot. Date: Tue, 10 Mar 2009 16:27:55 +0100 Does http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/swap1.diff?r1=1.11;r2=1.12 fix the problem you reported? (see http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/113957) -Guido From owner-freebsd-geom@FreeBSD.ORG Thu Mar 12 08:13:19 2009 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 267D6106566C for ; Thu, 12 Mar 2009 08:13:19 +0000 (UTC) (envelope-from lavagecko@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.171]) by mx1.freebsd.org (Postfix) with ESMTP id EC7B48FC21 for ; Thu, 12 Mar 2009 08:13:18 +0000 (UTC) (envelope-from lavagecko@gmail.com) Received: by wf-out-1314.google.com with SMTP id 27so458450wfd.7 for ; Thu, 12 Mar 2009 01:13:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:from:to :content-type:content-transfer-encoding:mime-version:subject:date :x-mailer; bh=s2kepCWsqiUDy2KUuFfMKJ++xjrX6yLOWMaJ7FNMH4k=; b=qAJYMkR6Jk18r2rucBVhPMOxx5pWGVVUq1i9z7x6PU16fzJQXHas5B6LVvvltsdrWH CXEfpSP5pEuYZS/o8obrmk7cX4F7nkrOVbRllNrjgKoeMOKo2t51L3bq2apvJruXcHIc kUCQdk7VtZ5iYC/+Ofe8Q4HzqNx846ClChLis= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:from:to:content-type:content-transfer-encoding :mime-version:subject:date:x-mailer; b=Jt5tyrQ7mvQC859qjjuBbW7d/ERCrYXp2uugYq9IyaNY1MpbYnQM35sGVUnWiNTLMn SCXqor3w2COmShqs7/CaOI1KNexMDqb83slG158XUjHO0XguEeELlNGS9v9VOrwOFzgZ CMB8ksU/NSv4onIwjfRrRSL3QrDWP8CpdBq64= Received: by 10.143.165.19 with SMTP id s19mr2672758wfo.236.1236844323253; Thu, 12 Mar 2009 00:52:03 -0700 (PDT) Received: from ?192.168.1.103? ([216.155.218.13]) by mx.google.com with ESMTPS id 29sm1035574wfg.53.2009.03.12.00.52.02 (version=SSLv3 cipher=RC4-MD5); Thu, 12 Mar 2009 00:52:02 -0700 (PDT) Sender: Clayton Message-Id: <6D5ADA2B-9471-4404-892D-1DFAB9011C09@bitheaven.net> From: Clayton Fuller To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Thu, 12 Mar 2009 01:52:01 -0600 X-Mailer: Apple Mail (2.930.3) Subject: Safe to ignore GEOM warnings on ZFS raidz? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2009 08:13:19 -0000 I am setting up a new home file server on CURRENT-8.0 using 4 1.5 TB SATA drives in a ZFS raidz pool I created the pool without first partitioning or labeling the drives. during the boot sequence, I get the following warnings for each of the drives: GEOM: ad6: corrupt or invalid GPT detected. GEOM: ad6: GPT rejected -- may not be recoverable. here's the drive info (I have 3 identical drives at ad8, ad12 and ad14) ad6: 1430799MB at ata3-master SATA300 The storage pool seems to work fine, as tested by transferring nearly a terabyte of data, simulating a failed drive, resilvering, etc and all seems to be working well. invoking the zpool scrub command will bring up the corrupt GPT errors again, but all other read/write operations on my storage pool seem to be fine. Is GEOM in any way necessary for managing this ZFS pool? Can I safely ignore the warnings? Is there a better way to configure this to keep GEOM happy? I'd be happy to supply more specifics if germane, but thought I'd try to keep it simple. Any suggestions would be greatly appreciated. -Clayton From owner-freebsd-geom@FreeBSD.ORG Thu Mar 12 10:19:04 2009 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4269106564A for ; Thu, 12 Mar 2009 10:19:04 +0000 (UTC) (envelope-from ulf.lilleengen@gmail.com) Received: from mail-ew0-f166.google.com (mail-ew0-f166.google.com [209.85.219.166]) by mx1.freebsd.org (Postfix) with ESMTP id 69AAD8FC08 for ; Thu, 12 Mar 2009 10:19:04 +0000 (UTC) (envelope-from ulf.lilleengen@gmail.com) Received: by ewy10 with SMTP id 10so441278ewy.43 for ; Thu, 12 Mar 2009 03:19:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=e3n7pDUzxtoNV1gNYVMWoaymXj5Aom0aZu08gK1ZfIQ=; b=h7bwelchEiUOcKX8TvtkKwVZvrqyCvSclRFWn8AgQRg0ZXF2CvpbRkQjLfzxB9sZ9D bQhcMzKnu3VREx+aZWYeSDZx/b/sppW11SyvUH9CT5yfY9fbwBrY6lNczBMgOuHRUmwg JQUoZFEVlmjsKIH+1FYJcBdsXXRNZtX7g7vq4= 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; b=xgZDGMFSOvtpbpDCOx4r6FEEJghoPVzzxhUWHxvcpDbN7eqLMsq7EDAR5FwmJwMm4F FwJv5wTjfyQ4J0sKj1ulADOyuykXLsLKR1TofmOP5ZcpwzXV0E/oV3eT5tP/Vwe+BMKP 081Bav9kGawE7Xfwh6nTbmr+BdmKei2chXIXg= MIME-Version: 1.0 Received: by 10.216.8.212 with SMTP id 62mr3888813wer.160.1236851826445; Thu, 12 Mar 2009 02:57:06 -0700 (PDT) In-Reply-To: <6D5ADA2B-9471-4404-892D-1DFAB9011C09@bitheaven.net> References: <6D5ADA2B-9471-4404-892D-1DFAB9011C09@bitheaven.net> Date: Thu, 12 Mar 2009 10:57:06 +0100 Message-ID: <917871cf0903120257u40537e4fp47b6d3ab973f706@mail.gmail.com> From: Ulf Lilleengen To: Clayton Fuller Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-geom@freebsd.org Subject: Re: Safe to ignore GEOM warnings on ZFS raidz? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2009 10:19:05 -0000 On Thu, Mar 12, 2009 at 8:52 AM, Clayton Fuller wrote: > I am setting up a new home file server on CURRENT-8.0 using 4 1.5 TB SATA > drives in a ZFS raidz pool > I created the pool without first partitioning or labeling the drives. > > during the boot sequence, I get the following warnings for each of the > drives: > GEOM: ad6: corrupt or invalid GPT detected. > GEOM: ad6: GPT rejected -- may not be recoverable. > > here's the drive info (I have 3 identical drives at ad8, ad12 and ad14) > ad6: 1430799MB at ata3-master SATA300 > > The storage pool seems to work fine, as tested by transferring nearly a > terabyte of data, simulating a failed drive, resilvering, etc and all seems > to be working well. > > invoking the zpool scrub command will bring up the corrupt GPT > errors again, but all other read/write operations on my storage pool seem to > be fine. > > Is GEOM in any way necessary for managing this ZFS pool? Can I safely > ignore the warnings? Is there a better way to configure this to keep GEOM > happy? > This has not necessarily anything to do with the pool itself, but gpart will display this message in case it finds remains of an old GPT partition. I think you can ignore the warnings. At least they have posed no problem from me for a while now. > > I'd be happy to supply more specifics if germane, but thought I'd try to > keep it simple. > > Any suggestions would be greatly appreciated. > > -Clayton > _______________________________________________ > freebsd-geom@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-geom > To unsubscribe, send any mail to "freebsd-geom-unsubscribe@freebsd.org" > -- Ulf Lilleengen From owner-freebsd-geom@FreeBSD.ORG Fri Mar 13 17:57:43 2009 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13D2A106566B for ; Fri, 13 Mar 2009 17:57:43 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 4EBF28FC0A for ; Fri, 13 Mar 2009 17:57:41 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA15114; Fri, 13 Mar 2009 19:57:40 +0200 (EET) (envelope-from avg@freebsd.org) Message-ID: <49BA9E93.4060609@freebsd.org> Date: Fri, 13 Mar 2009 19:57:39 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.19 (X11/20090110) MIME-Version: 1.0 To: freebsd-geom@freebsd.org, freebsd-fs@freebsd.org References: <4911C3E9.405@icyb.net.ua> <49198A1A.3080600@icyb.net.ua> <49227875.6090902@icyb.net.ua> <93FC5F5D-91CD-450B-B08D-5C5EC5A1C880@mac.com> <4922FB81.50608@icyb.net.ua> In-Reply-To: <4922FB81.50608@icyb.net.ua> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: zfs: affected by geom_(mbr|bsd) => geom_part_(mbr|bsd) ? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2009 17:57:43 -0000 Very belated but somebody reading archives might find this useful. Only today I discovered zdb command and its -C option: $ zdb -C tank version=6 name='tank' state=0 txg=1997530 pool_guid=15723282379537418671 hostid=714261228 hostname='' vdev_tree type='root' id=0 guid=15723282379537418671 children[0] type='disk' id=0 guid=1732303387090405178 path='/dev/ad6s2d' devid='ad:GEA534RF0TK35A' whole_disk=0 metaslab_array=14 metaslab_shift=32 ashift=9 asize=493659881472 DTL=182 on 18/11/2008 19:29 Andriy Gapon said the following: > I just remembered that I saved old zpool.cache file before "migrating" > the pool. > I looked at the diff of hexdumps and there are a number of differences, > it's hard to understand them because the file is binary (actually it > seems to contain serialized name-value pairs), but one difference is > prominent: > ... > 00000260 64 65 76 69 64 00 00 00 00 00 00 09 00 00 00 01 > |devid...........| > ... > -00000270 00 00 00 15 61 64 3a 47 45 41 35 33 34 52 46 30 > |....ad:GEA534RF0| > -00000280 54 4b 33 35 41 73 31 73 33 00 00 00 00 00 00 28 > |TK35As1s3......(| > ... > +00000270 00 00 00 11 61 64 3a 47 45 41 35 33 34 52 46 30 > |....ad:GEA534RF0| > +00000280 54 4b 33 35 41 00 00 00 00 00 00 28 00 00 00 28 > |TK35A......(...(| > ... > > It looks like old "devid" value is "ad:GEA534RF0TK35As1s3" and new one > is "ad:GEA534RF0TK35A". Just a reminder: actual zpool device is ad6s2d. > > The new value is what is reported by diskinfo: > $ diskinfo -v ad6 > ad6 > ... > ad:GEA534RF0TK35A # Disk ident. > > $ diskinfo -v ad6s2 > ad6s2 > ... > ad:GEA534RF0TK35A # Disk ident. > > $ diskinfo -v ad6s2d > ad6s2d > ... > ad:GEA534RF0TK35A # Disk ident. > > Hmm, "indent" is reported to be the same for all three entities. > > I don't remember what diskinfo reported with pre-gpart kernel, but I > suspect that it was something different. > Could anybody please check this? (on 7.X machine without GEOM_PART). > > I quickly glimpsed through sources and it seems that this comes from > DIOCGIDENT GEOM ioctl i.e. "GEOM::ident" attribute. It seems that > geom_slice.c code has some special handling for that. > -- Andriy Gapon