From owner-freebsd-geom@FreeBSD.ORG Mon Nov 23 11:06:55 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 F3BC6106566C for ; Mon, 23 Nov 2009 11:06:54 +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 E0D5D8FC0A for ; Mon, 23 Nov 2009 11:06:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nANB6suv070129 for ; Mon, 23 Nov 2009 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nANB6sTn070127 for freebsd-geom@FreeBSD.org; Mon, 23 Nov 2009 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 Nov 2009 11:06:54 GMT Message-Id: <200911231106.nANB6sTn070127@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, 23 Nov 2009 11:06:55 -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/140352 geom [geom] gjournal + glabel not working o kern/139847 geom [geom_mbr] load/unload causes system to hang o kern/135898 geom [geom] Severe filesystem corruption - large files or l o kern/134922 geom [gmirror] [panic] kernel panic when use fdisk on disk o kern/134113 geom [geli] Problem setting secondary GELI key o kern/134044 geom [geom] gmirror(8) overwrites fs with stale data from r o kern/133931 geom [geli] [request] intentionally wrong password to destr o bin/132845 geom [geom] [patch] ggated(8) does not close files opened a o kern/132273 geom glabel(8): [patch] failing on journaled partition f kern/132242 geom [gmirror] gmirror.ko fails to fully initialize o kern/131353 geom [geom] gjournal(8) kernel lock p docs/130548 geom [patch] gjournal(8) man page is missing sysctls 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 f kern/128276 geom [gmirror] machine lock up when gmirror module is used f 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 f kern/124294 geom [geom] gmirror(8) have inappropriate logic when workin o kern/123962 geom [panic] [gjournal] gjournal (455Gb data, 8Gb journal), o kern/123122 geom [geom] GEOM / gjournal kernel lock o kern/122738 geom [geom] gmirror list "losts consumers" after gmirror de 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/120091 geom [geom] [geli] [gjournal] geli does not prompt for pass 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 o kern/115856 geom [geli] ZFS thought it was degraded when it should have o 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/113885 geom [gmirror] [patch] improved gmirror balance algorithm 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 o kern/88601 geom [geli] geli cause kernel panic under heavy disk usage 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 53 problems total. From owner-freebsd-geom@FreeBSD.ORG Tue Nov 24 17:53:31 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 B423E106566C for ; Tue, 24 Nov 2009 17:53:31 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from QMTA13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by mx1.freebsd.org (Postfix) with ESMTP id 637648FC12 for ; Tue, 24 Nov 2009 17:53:31 +0000 (UTC) Received: from OMTA14.westchester.pa.mail.comcast.net ([76.96.62.60]) by QMTA13.westchester.pa.mail.comcast.net with comcast id 91851d01T1HzFnQ5D5gGTE; Tue, 24 Nov 2009 17:40:16 +0000 Received: from [192.168.2.164] ([206.210.89.202]) by OMTA14.westchester.pa.mail.comcast.net with comcast id 95g31d0034Mx3R23a5g5lE; Tue, 24 Nov 2009 17:40:14 +0000 Message-ID: <4B0C1A72.3000301@comcast.net> Date: Tue, 24 Nov 2009 12:40:02 -0500 From: Steve Polyack User-Agent: Thunderbird 2.0.0.23 (X11/20090902) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org, freebsd-stable , freebsd-geom@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Panic possibly related to glabel/geom and siis(4) 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: Tue, 24 Nov 2009 17:53:31 -0000 I have a system running 8.0-PRERELEASE with multiple drives and SATA port multipliers (siis controllers and PMPs). All of the attached drives are labeled via glabel(8) and then included into a ZFS pool. During some testing to determine how the system would react to a dead drive (simulated by physically removing a drive during operation), I was able to produce a panic. Now, I know that the SATA PMP and siis(4) code to handle and recover from device errors is incomplete, but I believe the crash may be particular to using glabel'd drives. Basically, after removing a drive while the zpool is in use and issues 'camcontrol reset' and 'rescan' on the appropriate bus, the physical device associated with the drive disappears. In this case: (pass5:siisch7:0:15:0): lost device (pass5:siisch7:0:15:0): removing device entry (ada2:siisch7:0:0:0): lost device and /dev/ada2 disappears. However, the associated glabel /dev/label/bigdisk07 remains. Since my ZFS pool is created based on the drive glabels, I believe this is why ZFS never notices the drives disappear either. Do glabels typically go away after a physical device is lost? Should this not be the case? After some runtime with the physical device missing, a kernel panic is produced: ada2:siisch7:0:0:0): Synchronize cache failed (ada2:siisch7:0:0:0): removing device entry Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 14 fault virtual address = 0x48 fault code = supervisor write data, page not present instruction pointer = 0x20:0xffffffff8035f375 stack pointer = 0x28:0xffffff800006db60 frame pointer = 0x28:0xffffff800006db70 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 2 (g_event) [thread pid 2 tid 100014 ] Stopped at _mtx_lock_flags+0x15: lock cmpxchgq %rsi,0x18(%rdi) db> bt Tracing pid 2 tid 100014 td 0xffffff00014d4ab0 _mtx_lock_flags() at _mtx_lock_flags+0x15 vdev_geom_release() at vdev_geom_release+0x33 vdev_geom_orphan() at vdev_geom_orphan+0x15c g_run_events() at g_run_events+0x104 g_event_procbody() at g_event_procbody+0x55 fork_exit() at fork_exit+0x118 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff800006dd30, rbp = 0 --- I'm open to try patches and other suggestions. Thanks. From owner-freebsd-geom@FreeBSD.ORG Sat Nov 28 01:05:05 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 25052106566C for ; Sat, 28 Nov 2009 01:05:05 +0000 (UTC) (envelope-from freebsd-geom@jrv.org) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.freebsd.org (Postfix) with ESMTP id C8A8C8FC08 for ; Sat, 28 Nov 2009 01:05:04 +0000 (UTC) Received: from kremvax.housenet.jrv (kremvax.housenet.jrv [192.168.3.124]) by mail.jrv.org (8.14.3/8.14.3) with ESMTP id nAS0IPh3098601 for ; Fri, 27 Nov 2009 18:18:25 -0600 (CST) (envelope-from freebsd-geom@jrv.org) Authentication-Results: mail.jrv.org; domainkeys=pass (testing) header.from=freebsd-geom@jrv.org DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: x-enigmail-version:content-type:content-transfer-encoding; b=szP0LyhwEeA98OWmPWbk4rsrF21ROiriEiWwhBiutw4ZguRxtteCCM+toYkTQ1VWQ Kyyos1CbnSRogDLwBdCbXyxbhQU4fOuoT3egcMzrUz712Q82fIbIzLPdsI7WV//WZ/1 1yGBUmHHs0Gs71l8Ym0YWkFKklYAEVYc6PENW/Q= Message-ID: <4B106C51.7070905@jrv.org> Date: Fri, 27 Nov 2009 18:18:25 -0600 From: "James R. Van Artsdalen" User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: freebsd-geom@freebsd.org X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: help adding device serial numbers to /dev namespace? 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: Sat, 28 Nov 2009 01:05:05 -0000 Can anyone give me suggestions on how to implement putting disk driver serial numbers in the /dev namespace, much as UFS ID's are put there now? I want to propose adding the disk drive's hardware serial number, i.e., for this # camcontrol identify ada0 pass0: ATA/ATAPI-7 SATA 1.x device pass0: 150.000MB/s transfers protocol ATA/ATAPI-7 SATA 1.x device model ST3750640AS firmware revision 3.AAJ serial number 3QD0NWQT ... I would add a name like /dev/serialnum/3QD0NWQT. This differs from the current name schemes I know of in that it describes the whole disk and not any particular partition or region, and no on-disk storage is needed. I think this needs to be done in GEOM, as a result of disk_create() and using d_ident, but I'm getting lost and need some guidance to do an example patch to "formally" propose the idea. The immediate use today is for ZFS. From owner-freebsd-geom@FreeBSD.ORG Sat Nov 28 08:51:37 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 EEDEA106566B for ; Sat, 28 Nov 2009 08:51:37 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 7ECA68FC12 for ; Sat, 28 Nov 2009 08:51:37 +0000 (UTC) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id 189747E995; Sat, 28 Nov 2009 08:51:36 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.3/8.14.3) with ESMTP id nAS8pspQ001786; Sat, 28 Nov 2009 08:51:54 GMT (envelope-from phk@critter.freebsd.dk) To: "James R. Van Artsdalen" From: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 27 Nov 2009 18:18:25 CST." <4B106C51.7070905@jrv.org> Date: Sat, 28 Nov 2009 08:51:54 +0000 Message-ID: <1785.1259398314@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: freebsd-geom@freebsd.org Subject: Re: help adding device serial numbers to /dev namespace? 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: Sat, 28 Nov 2009 08:51:38 -0000 In message <4B106C51.7070905@jrv.org>, "James R. Van Artsdalen" writes: >Can anyone give me suggestions on how to implement putting disk driver >serial numbers in the /dev namespace, much as UFS ID's are put there now? Something like, or possibly g_label. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-geom@FreeBSD.ORG Sat Nov 28 15:51:12 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 93B92106566B; Sat, 28 Nov 2009 15:51:12 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 57C498FC0C; Sat, 28 Nov 2009 15:51:12 +0000 (UTC) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id F10F87E839; Sat, 28 Nov 2009 15:51:10 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.3/8.14.3) with ESMTP id nASFpS5N015909; Sat, 28 Nov 2009 15:51:28 GMT (envelope-from phk@critter.freebsd.dk) To: Pawel Jakub Dawidek From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 28 Nov 2009 09:57:59 +0100." <20091128085759.GW1567@garage.freebsd.pl> Date: Sat, 28 Nov 2009 15:51:28 +0000 Message-ID: <15908.1259423488@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: "James R. Van Artsdalen" , freebsd-geom@FreeBSD.org Subject: Re: help adding device serial numbers to /dev namespace? 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: Sat, 28 Nov 2009 15:51:12 -0000 In message <20091128085759.GW1567@garage.freebsd.pl>, Pawel Jakub Dawidek write s: >This should be very simple to do, I think I even done that in the past, >but before we do it, I want trasz@ to commit his patch to selectively >turn on and off submodules in glabel. Way too much stuff is created by >glabel these days. It's a relevant question if g_label should tie into the "device-on-demand" eventhandler and only produce some of the more obscure names if asked to. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-geom@FreeBSD.ORG Sat Nov 28 16:29:12 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 E896B1065670 for ; Sat, 28 Nov 2009 16:29:12 +0000 (UTC) (envelope-from marius@nuenneri.ch) Received: from mail-ew0-f221.google.com (mail-ew0-f221.google.com [209.85.219.221]) by mx1.freebsd.org (Postfix) with ESMTP id 8CBF38FC14 for ; Sat, 28 Nov 2009 16:29:12 +0000 (UTC) Received: by ewy21 with SMTP id 21so2924663ewy.13 for ; Sat, 28 Nov 2009 08:29:11 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.85.68 with SMTP id t46mr727040wee.114.1259425751196; Sat, 28 Nov 2009 08:29:11 -0800 (PST) In-Reply-To: <4B106C51.7070905@jrv.org> References: <4B106C51.7070905@jrv.org> From: =?ISO-8859-1?Q?Marius_N=FCnnerich?= Date: Sat, 28 Nov 2009 17:28:51 +0100 Message-ID: To: "James R. Van Artsdalen" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-geom@freebsd.org Subject: Re: help adding device serial numbers to /dev namespace? 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: Sat, 28 Nov 2009 16:29:13 -0000 On Sat, Nov 28, 2009 at 01:18, James R. Van Artsdalen wrote: > Can anyone give me suggestions on how to implement putting disk driver > serial numbers in the /dev namespace, much as UFS ID's are put there now? > > I want to propose adding the disk drive's hardware serial number, i.e., > for this > > # camcontrol identify ada0 > pass0: ATA/ATAPI-7 SATA 1.x device > pass0: 150.000MB/s transfers > > protocol =A0 =A0 =A0 =A0 =A0 =A0 =A0ATA/ATAPI-7 SATA 1.x > device model =A0 =A0 =A0 =A0 =A0ST3750640AS > firmware revision =A0 =A0 3.AAJ > serial number =A0 =A0 =A0 =A0 3QD0NWQT > ... > > I would add a name like /dev/serialnum/3QD0NWQT. =A0This differs from the > current name schemes I know of in that it describes the whole disk and > not any particular partition or region, and no on-disk storage is needed. > > I think this needs to be done in GEOM, as a result of disk_create() and > using d_ident, but I'm getting lost and need some guidance to do an > example patch to "formally" propose the idea. > > The immediate use today is for ZFS. If I remember correctly ivoras@ already proposed a patch like this.