From owner-freebsd-current@FreeBSD.ORG Wed Sep 27 07:19:17 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C1E716A47B; Wed, 27 Sep 2006 07:19:17 +0000 (UTC) (envelope-from ivoras@fer.hr) Received: from ls405.htnet.hr (ls405.t-com.hr [195.29.150.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B2D043D77; Wed, 27 Sep 2006 07:19:07 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from ls422.t-com.hr (ls422.t-com.hr [195.29.150.237]) by ls405.htnet.hr (Postfix) with ESMTP id F34F3143C0D; Wed, 27 Sep 2006 09:19:05 +0200 (CEST) Received: from ls422.t-com.hr (localhost.localdomain [127.0.0.1]) by ls422.t-com.hr (Qmlai) with ESMTP id E63FCC9004A; Wed, 27 Sep 2006 09:19:05 +0200 (CEST) X-Envelope-Sender: ivoras@fer.hr Received: from [89.172.53.253] (89-172-53-253.adsl.net.t-com.hr [89.172.53.253])by ls422.t-com.hr (Qmlai) with ESMTP id 565671308075; Wed, 27 Sep 2006 09:19:04 +0200 (CEST) Message-ID: <451A25F2.6050106@fer.hr> Date: Wed, 27 Sep 2006 09:19:14 +0200 From: Ivan Voras User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Yoshihiro Ota References: <44EF12F6.3000806@fer.hr> <20060925213522.4c9eacb7.ota@j.email.n e.jp> <4518DE53.9070101@fer.hr> <20060926221547.1ae6f72a.ota@j.email.ne.jp> In-Reply-To: <20060926221547.1ae6f72a.ota@j.email.ne.jp> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-imss-version: 2.042 X-imss-result: Passed X-imss-scores: Clean:60.30964 C:2 M:4 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) Cc: geom@freebsd.org, current@freebsd.org Subject: Re: Announcing: gvirstor X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Sep 2006 07:19:17 -0000 Yoshihiro Ota wrote: > Reading "gvirstor implementation details", it is not intended to remove components, is it? If not, it will a grate benefit to allow "take-off" components as some device may go bad while other devices are still functioning when a virstor is created with multiple devices. If it's a much requested feature, I'll implement it; as it is currently done, only unused components at the end of the list of components can be removed. > I tried it anyway. It seemed that I was able to detach md3 and then add md4. Md3 was not used at all when I removed; status only displaed md2 but I was not sure if it was removed perfectly in gvirstor as no mention in the document. Later, I was not able to add md3 back again. > > These are the command lines I tried > # mount /dev/virstor/test /mnt/tmp > # tar xf ports.tar.bz -C /mnt/tmp & > # ./gvirstor remove test md3 Ok, I'll try this situation at my development machine. > # ./gvirstor add test md4 > # ./gvirstor status test > # ./gvirstor add test md3 > > Kernel paniced after a while. Many things were going so it was not sure that gvirstor was the cause of the problem. Kernel panic message may tell you what system panicked. > I will try as time permitts. Thank you.