Date: Wed, 4 Feb 2009 07:01:03 GMT From: Alexei Volkov <Alexei.Volkov@softlynx.ru> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/131353: gjournal kernel lock Message-ID: <200902040701.n147133R085595@www.freebsd.org> Resent-Message-ID: <200902040710.n147A1EA057887@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 131353 >Category: kern >Synopsis: gjournal kernel lock >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Feb 04 07:10:00 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Alexei Volkov >Release: 7.1-RELEASE-p1 >Organization: SoftLynx >Environment: FreeBSD server 7.1-RELEASE-p1 FreeBSD 7.1-RELEASE-p1 #0: Thu Jan 22 11:14:58 MSK 2009 root@server:/usr/obj/i386/usr/src/sys/GENERIC i386 >Description: 7.1-RELEASE-p1 FreeBSD server 7.1-RELEASE-p1 FreeBSD 7.1-RELEASE-p1 #0: Thu Jan 22 11:14:58 MSK 2009 root@server:/usr/obj/i386/usr/src/sys/GENERIC i386 I have several machines running with identical config: 1. gmirror on two SATA devices 2. single gjournal FS configured as described under PR #129674 and mounted to root. 3. Periodical night snapshoting with mount -o snapshot Currently there is stable issue with kernel lock up caused by snapshoting with mount -u -o snapshot /.snap/snapshot.0 / After hard reset the PR #129674 comes to scene. >How-To-Repeat: Configure FS the way PR #129674 described And take snapshots couple times until it locks up. mount -u -o snapshot /.snap/snapshot.0 / mount -u -o snapshot /.snap/snapshot.1 / mount -u -o snapshot /.snap/snapshot.2 / .. and so on. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200902040701.n147133R085595>