Date: Sun, 27 Apr 2008 00:30:23 GMT From: mike durller <mike.durller@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: i386/123122: GEOM / gjournal kernel lock Message-ID: <200804270030.m3R0UNOr022493@www.freebsd.org> Resent-Message-ID: <200804270040.m3R0e0WE044870@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 123122 >Category: i386 >Synopsis: GEOM / gjournal kernel lock >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Apr 27 00:40:00 UTC 2008 >Closed-Date: >Last-Modified: >Originator: mike durller >Release: 7.0-RELEASE >Organization: >Environment: 7.0-Release Generic i386, stock kernel, atapci0: SiI 3124 SATA300 PCI-X controller >Description: The FreeBSD-7 stock kernel locks 1/4 way thru newfs "writing superblocks" to a three drive GEOM graid3 array when gjournal is active. >How-To-Repeat: Simply make a graid3 label, activate a gjournal label, and make a new filesystem with newfs. >Fix: >Release-Note: >Audit-Trail: >Unformatted: >> graid3 label gr0 ad4 ad6 ad8 >> gjournal label raid3/gr0 >> newfs -J -O 2 raid3/gr0.journal It makes no difference if the array is degraded, it still locks up. Also, when gjournal is not active, newfs is issued and works normally.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200804270030.m3R0UNOr022493>