From owner-freebsd-geom@FreeBSD.ORG Sun Nov 15 20:45:08 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 474C71065672 for ; Sun, 15 Nov 2009 20:45:08 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [IPv6:2001:4068:10::3]) by mx1.freebsd.org (Postfix) with ESMTP id 0662F8FC08 for ; Sun, 15 Nov 2009 20:45:08 +0000 (UTC) Received: from localhost (amavis.fra.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 12F4641C74D for ; Sun, 15 Nov 2009 21:45:07 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([192.168.74.103]) by localhost (amavis.fra.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id k1RmEJUBzcdG for ; Sun, 15 Nov 2009 21:45:06 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id 36BB141C75D; Sun, 15 Nov 2009 21:45:06 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 874044448E6 for ; Sun, 15 Nov 2009 20:44:35 +0000 (UTC) Date: Sun, 15 Nov 2009 20:44:35 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: freebsd-geom@freebsd.org Message-ID: <20091115203253.R37440@maildrop.int.zabbadoz.net> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: gjournal + gptid/ un"stop"able 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, 15 Nov 2009 20:45:08 -0000 Hi, I just read the previous thread via the list archive. As of late on HEAD something changed that doesn't allow one to "stop" gjournal anymore and get rid of it. I have been using this same setup for months if not more than a year without problems. Whatever was added introduced an architectural problem. Either /dev/da*.journal exists or when that is stopped a journal etc. shows up with the "cryptic" names in /dev/gptid/....journal. If you stop that, the /dev/da*.journal is back. This essentially means that once gjournal is loaded, one is unable to unload it again, unless ones force a "detach"/"stop" on all lower providers. This essentially means that one can no longer safely shut down without the risk of losing/scrambling data. I guess the "ufsid/" things mentioned formerly has the same problem. What are the possible solutions to that? /bz -- Bjoern A. Zeeb It will not break if you know what you are doing.