From owner-freebsd-geom@FreeBSD.ORG Sun Feb 21 06:44:09 2010 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 18398106566C for ; Sun, 21 Feb 2010 06:44:09 +0000 (UTC) (envelope-from bartosz@fabianowski.eu) Received: from dd15624.kasserver.com (dd15624.kasserver.com [85.13.136.215]) by mx1.freebsd.org (Postfix) with ESMTP id CFA5D8FC0A for ; Sun, 21 Feb 2010 06:44:08 +0000 (UTC) Received: from taiko.lan (84-203-79-36.mysmart.ie [84.203.79.36]) by dd15624.kasserver.com (Postfix) with ESMTP id 3B5942C25E9FF for ; Sun, 21 Feb 2010 07:12:57 +0100 (CET) Message-ID: <4B80CEE3.80909@fabianowski.eu> Date: Sun, 21 Feb 2010 06:12:51 +0000 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100212 Thunderbird/3.0.1 MIME-Version: 1.0 To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: gjournal failing to do its job 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, 21 Feb 2010 06:44:09 -0000 Good day I recently set up a brand new 8-STABLE box with UFS2 + gjournal. After a hang and hard reboot, I noticed that the setup is not working. File systems came up inconsistent without the system even noticing. I had to manually run fsck in single user mode to get back to a consistent state. The setup is nested as follows: Drive: ada0 Slice (MBR partition): ada0s2 geli full drive encryption: ada0s2.eli gjournal: ada0s2.eli.journal bsdlabel: ada0s2.eli.journala - ada0s2.eli.journalg Partitions a, d, e, f and g are UFS2 file systems. Partition b is swap. As the hard drive is fully encrypted, the system boots off a USB key containing the boot loader, kernel and fstab. In the fstab, file systems are addressed by their volume labels and swap by a label set with glabel. As it appeared gjournal was working fine, I had set the gjournal flag on all UFS2 file systems and mounted them async. After the crash and reboot, gjournal reported "consistent" state. Then, a message informed me that / had not been unmounted cleanly and fsck ran on that one file system. For the other file systems (located in partitions d, e, f and g above), I got no messages of any sort. However, once the system was up, they were clearly inconsistent. A manual fsck run revealed serious inconsistencies such as unallocated inodes. The journal had clearly failed to do its job. Could anyone point me to what I am doing wrong? I know I have nested several GEOM providers inside each other. I was under the impression this was the very concept behind GEOM. Is it that I cannot have a single journal with multiple bsdlabel partitions inside? Again, it would seem GEOM allows this - and I have found mailing list messages suggesting others have done this before. On a related note, it would appear that there is no way to verify gjournal is actually active on a file system. I can set the journaling flag on any UFS2 partition - whether gjournal actually works or not. Is there some way to ensure that all file systems with journaling flag set are actually journaled? The "gjournal list" command tells me that ada0s2.eli is a provider and ada0s2.eli.journal a consumer. But are all bsdlabel partitions inside the consumer covered as well? There seems to be no tool that can tell me that. I am hoping someone on the list can shed some light on this. As a stop-gap measure, I have enabled softupdates on the file systems and removed the async flags from my fstab. I really would like to use journaling though - if I can find a way to enable it and make sure it is actually working. Thanks, - Bartosz Fabianowski From owner-freebsd-geom@FreeBSD.ORG Sun Feb 21 08:25:20 2010 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 972A01065670 for ; Sun, 21 Feb 2010 08:25:20 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello089077043238.chello.pl [89.77.43.238]) by mx1.freebsd.org (Postfix) with ESMTP id D8A9A8FC08 for ; Sun, 21 Feb 2010 08:25:19 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 4927745E35; Sun, 21 Feb 2010 09:25:17 +0100 (CET) Received: from localhost (chello089077043238.chello.pl [89.77.43.238]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 49C8D4569A; Sun, 21 Feb 2010 09:25:12 +0100 (CET) Date: Sun, 21 Feb 2010 09:25:09 +0100 From: Pawel Jakub Dawidek To: Bartosz Fabianowski Message-ID: <20100221082508.GL1617@garage.freebsd.pl> References: <4B80CEE3.80909@fabianowski.eu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="F7w+4yMapWozG0Ib" Content-Disposition: inline In-Reply-To: <4B80CEE3.80909@fabianowski.eu> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-geom@freebsd.org Subject: Re: gjournal failing to do its job 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, 21 Feb 2010 08:25:20 -0000 --F7w+4yMapWozG0Ib Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Feb 21, 2010 at 06:12:51AM +0000, Bartosz Fabianowski wrote: > Good day >=20 > I recently set up a brand new 8-STABLE box with UFS2 + gjournal. After a= =20 > hang and hard reboot, I noticed that the setup is not working. File=20 > systems came up inconsistent without the system even noticing. I had to= =20 > manually run fsck in single user mode to get back to a consistent state. >=20 > The setup is nested as follows: >=20 > Drive: ada0 > Slice (MBR partition): ada0s2 > geli full drive encryption: ada0s2.eli > gjournal: ada0s2.eli.journal > bsdlabel: ada0s2.eli.journala - ada0s2.eli.journalg File system should be placed directly on .journal provider. Please consult EXAMPLES section in gjournal(8). --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --F7w+4yMapWozG0Ib Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkuA7eQACgkQForvXbEpPzSh/QCgzM0KZz9OOqi49YO6YB+ZYod+ LlgAn0nDwGsewclRq2xCY5N/ECt7A7gL =kUrf -----END PGP SIGNATURE----- --F7w+4yMapWozG0Ib-- From owner-freebsd-geom@FreeBSD.ORG Mon Feb 22 11:06:58 2010 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 428E11065676 for ; Mon, 22 Feb 2010 11:06:58 +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 17E9A8FC25 for ; Mon, 22 Feb 2010 11:06:58 +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 o1MB6vhB039701 for ; Mon, 22 Feb 2010 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o1MB6vk0039699 for freebsd-geom@FreeBSD.org; Mon, 22 Feb 2010 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 22 Feb 2010 11:06:57 GMT Message-Id: <201002221106.o1MB6vk0039699@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, 22 Feb 2010 11:06:58 -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/143455 geom gstripe(8) in RELENG_8 (31st Jan 2010) broken o kern/142563 geom [geom] [hang] ioctl freeze in zpool f kern/142365 geom [geom] FreeBSD RAID1 (gmirror) is much slower than Lin o kern/141740 geom [geom] gjournal(8): g_journal_destroy concurrent error o kern/140352 geom [geom] gjournal + glabel not working o kern/139847 geom [geom_mbr] [patch] 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 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/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/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 54 problems total. From owner-freebsd-geom@FreeBSD.ORG Mon Feb 22 16:54:11 2010 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 529EB1065694 for ; Mon, 22 Feb 2010 16:54:11 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd15624.kasserver.com (dd15624.kasserver.com [85.13.136.215]) by mx1.freebsd.org (Postfix) with ESMTP id 135568FC16 for ; Mon, 22 Feb 2010 16:54:10 +0000 (UTC) Received: from [192.168.8.150] (84-203-79-36.mysmart.ie [84.203.79.36]) by dd15624.kasserver.com (Postfix) with ESMTP id 9BEDC2C1FFFC2; Mon, 22 Feb 2010 17:31:52 +0100 (CET) Message-ID: <4B82B181.90707@chillt.de> Date: Mon, 22 Feb 2010 16:32:01 +0000 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Shredder/3.0.1 MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <4B80CEE3.80909@fabianowski.eu> <20100221082508.GL1617@garage.freebsd.pl> In-Reply-To: <20100221082508.GL1617@garage.freebsd.pl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-geom@freebsd.org Subject: Re: gjournal failing to do its job 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, 22 Feb 2010 16:54:11 -0000 > File system should be placed directly on .journal provider. > Please consult EXAMPLES section in gjournal(8). Thanks for clarifying that. I re-created all file systems with separate journals. Part of my question still stands though: Is there any way to tell whether a journal-enabled UFS file system (one created with the -J flag or with journaling enabled via tunefs) is actually properly residing on a gjournal provider? One can always find out the hard way - yank the power cable and see whether the journal works. But should there not be a way to verify that as far as GEOM and the file system layer are concerned, everything is set up correctly? - Bartosz From owner-freebsd-geom@FreeBSD.ORG Thu Feb 25 18:00:06 2010 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 100F0106566B for ; Thu, 25 Feb 2010 18:00:06 +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 D1BD98FC1C for ; Thu, 25 Feb 2010 18:00:05 +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 o1PI051R009090 for ; Thu, 25 Feb 2010 18:00:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o1PI05M9009089; Thu, 25 Feb 2010 18:00:05 GMT (envelope-from gnats) Date: Thu, 25 Feb 2010 18:00:05 GMT Message-Id: <201002251800.o1PI05M9009089@freefall.freebsd.org> To: freebsd-geom@FreeBSD.org From: Jaakko Heinonen Cc: Subject: Re: kern/89660: [vinum] [patch] [panic] due to g_malloc returning null in gv_drive_done X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jaakko Heinonen List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Feb 2010 18:00:06 -0000 The following reply was made to PR kern/89660; it has been noted by GNATS. From: Jaakko Heinonen To: bug-followup@FreeBSD.org, stijn@win.tue.nl Cc: Subject: Re: kern/89660: [vinum] [patch] [panic] due to g_malloc returning null in gv_drive_done Date: Thu, 25 Feb 2010 19:50:51 +0200 This has been probably fixed in r190507. Can you confirm? http://www.freebsd.org/cgi/query-pr.cgi?pr=89660 From owner-freebsd-geom@FreeBSD.ORG Thu Feb 25 18:31:26 2010 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 6EE031065672; Thu, 25 Feb 2010 18:31:26 +0000 (UTC) (envelope-from jh@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 45F9C8FC0C; Thu, 25 Feb 2010 18:31:26 +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 o1PIVQN0043826; Thu, 25 Feb 2010 18:31:26 GMT (envelope-from jh@freefall.freebsd.org) Received: (from jh@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o1PIVPR9043822; Thu, 25 Feb 2010 18:31:25 GMT (envelope-from jh) Date: Thu, 25 Feb 2010 18:31:25 GMT Message-Id: <201002251831.o1PIVPR9043822@freefall.freebsd.org> To: stijn@win.tue.nl, jh@FreeBSD.org, freebsd-geom@FreeBSD.org, jh@FreeBSD.org From: jh@FreeBSD.org Cc: Subject: Re: kern/89660: [vinum] [patch] [panic] due to g_malloc returning null in gv_drive_done 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, 25 Feb 2010 18:31:26 -0000 Synopsis: [vinum] [patch] [panic] due to g_malloc returning null in gv_drive_done State-Changed-From-To: analyzed->feedback State-Changed-By: jh State-Changed-When: Thu Feb 25 18:30:44 UTC 2010 State-Changed-Why: Note that submitter has been asked for feedback. Responsible-Changed-From-To: freebsd-geom->jh Responsible-Changed-By: jh Responsible-Changed-When: Thu Feb 25 18:30:44 UTC 2010 Responsible-Changed-Why: Track. http://www.freebsd.org/cgi/query-pr.cgi?pr=89660 From owner-freebsd-geom@FreeBSD.ORG Thu Feb 25 19:54:45 2010 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 087A1106564A; Thu, 25 Feb 2010 19:54:45 +0000 (UTC) (envelope-from lulf@freebsd.org) Received: from hylle02.itea.ntnu.no (hylle02.itea.ntnu.no [IPv6:2001:700:300:3::101]) by mx1.freebsd.org (Postfix) with ESMTP id E8FD58FC21; Thu, 25 Feb 2010 19:54:43 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by hylle02.itea.ntnu.no (Postfix) with ESMTP id 303533124E; Thu, 25 Feb 2010 20:54:40 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at hylle02.itea.ntnu.no Received: from carrot (lynx.stud.ntnu.no [IPv6:2001:700:300:3::180]) by hylle02.itea.ntnu.no (Postfix) with ESMTP id 968F431245; Thu, 25 Feb 2010 20:54:39 +0100 (CET) Date: Thu, 25 Feb 2010 20:57:04 +0100 From: Ulf Lilleengen To: jh@FreeBSD.org Message-ID: <20100225195703.GA9894@carrot> Mail-Followup-To: jh@FreeBSD.org, stijn@win.tue.nl, freebsd-geom@FreeBSD.org References: <201002251831.o1PIVPR9043822@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201002251831.o1PIVPR9043822@freefall.freebsd.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: stijn@win.tue.nl, freebsd-geom@FreeBSD.org Subject: Re: kern/89660: [vinum] [patch] [panic] due to g_malloc returning null in gv_drive_done X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ...@carrot List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Feb 2010 19:54:45 -0000 On Thu, Feb 25, 2010 at 06:31:25PM +0000, jh@FreeBSD.org wrote: > Synopsis: [vinum] [patch] [panic] due to g_malloc returning null in gv_drive_done > > State-Changed-From-To: analyzed->feedback > State-Changed-By: jh > State-Changed-When: Thu Feb 25 18:30:44 UTC 2010 > State-Changed-Why: > Note that submitter has been asked for feedback. > > > Responsible-Changed-From-To: freebsd-geom->jh > Responsible-Changed-By: jh > Responsible-Changed-When: Thu Feb 25 18:30:44 UTC 2010 > Responsible-Changed-Why: > Track. > I'm pretty sure this can be closed. The implementation in 6.0 is totally different, and the panic happens in code that no longer exists. Ulf From owner-freebsd-geom@FreeBSD.ORG Thu Feb 25 19:57:40 2010 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 B6472106566B; Thu, 25 Feb 2010 19:57:40 +0000 (UTC) (envelope-from lulf@FreeBSD.org) Received: from hylle01.itea.ntnu.no (hylle01.itea.ntnu.no [IPv6:2001:700:300:3::100]) by mx1.freebsd.org (Postfix) with ESMTP id 0303B8FC13; Thu, 25 Feb 2010 19:57:40 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by hylle01.itea.ntnu.no (Postfix) with ESMTP id 2FED031E052; Thu, 25 Feb 2010 20:57:39 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at hylle01.itea.ntnu.no Received: from carrot (lynx.stud.ntnu.no [IPv6:2001:700:300:3::180]) by hylle01.itea.ntnu.no (Postfix) with ESMTP id D200B31E041; Thu, 25 Feb 2010 20:57:38 +0100 (CET) Date: Thu, 25 Feb 2010 21:00:02 +0100 From: Ulf Lilleengen To: jh@FreeBSD.org Message-ID: <20100225200002.GB9894@carrot> Mail-Followup-To: jh@FreeBSD.org, stijn@win.tue.nl, freebsd-geom@FreeBSD.org References: <201002251831.o1PIVPR9043822@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201002251831.o1PIVPR9043822@freefall.freebsd.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: stijn@win.tue.nl, freebsd-geom@FreeBSD.org Subject: Re: kern/89660: [vinum] [patch] [panic] due to g_malloc returning null in gv_drive_done 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, 25 Feb 2010 19:57:40 -0000 On Thu, Feb 25, 2010 at 06:31:25PM +0000, jh@FreeBSD.org wrote: > Synopsis: [vinum] [patch] [panic] due to g_malloc returning null in gv_drive_done > > State-Changed-From-To: analyzed->feedback > State-Changed-By: jh > State-Changed-When: Thu Feb 25 18:30:44 UTC 2010 > State-Changed-Why: > Note that submitter has been asked for feedback. > > > Responsible-Changed-From-To: freebsd-geom->jh > Responsible-Changed-By: jh > Responsible-Changed-When: Thu Feb 25 18:30:44 UTC 2010 > Responsible-Changed-Why: > Track. > I'm pretty sure this can be closed. The implementation in 6.0 is totally different, and the panic happens in code that no longer exists. Ulf