From owner-freebsd-questions Thu Jun 21 21:13:33 2001 Delivered-To: freebsd-questions@freebsd.org Received: from clmboh1-smtp3.columbus.rr.com (clmboh1-smtp3.columbus.rr.com [65.24.0.112]) by hub.freebsd.org (Postfix) with ESMTP id C4A7137B403; Thu, 21 Jun 2001 21:13:28 -0700 (PDT) (envelope-from wmoran@iowna.com) Received: from iowna.com (dhcp065-024-023-038.columbus.rr.com [65.24.23.38]) by clmboh1-smtp3.columbus.rr.com (8.11.2/8.11.2) with ESMTP id f5M4A9s05421; Fri, 22 Jun 2001 00:10:09 -0400 (EDT) Message-ID: <3B32C5BE.D388DCF9@iowna.com> Date: Fri, 22 Jun 2001 00:12:46 -0400 From: Bill Moran X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: Drew Derbyshire , questions@FreeBSD.org Subject: Re: Stopping / removing vinum segments References: <007701c0f6de$cef773b0$94cba8c0@xena> <3B2C2B84.8792D238@iowna.com> <000801c0f72b$f25931c0$94cba8c0@xena> <3B2CC068.2A0B6C01@iowna.com> <000801c0f748$ab47a880$94cba8c0@xena> <20010619112338.C58585@wantadilla.lemis.com> <002801c0fa6c$3d0f78d0$94cba8c0@xena> <20010622132151.X57186@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greg Lehey wrote: > >>> The problem with resetconfig is, if I had another volume which WAS > >>> live and active, the resetconfig would have smoked that as well. > >> > >> You shouldn't use resetconfig. Use commands like rm. (in shameless defense of myself, I only suggested resetconfig because he mentioned that the entire vinum configuration was wrong ;) > There's a good reason to use force here: you're damaging the > structure, potentially causing data loss. If you have detach the > objects first, you can remove them. But you'll need force to detach > anything which makes a hole in a volume address space. Makes sense now (didn't before) Perhaps a more informative error message under these circumstances would be helpful? Something to the effect of: "Detaching will destroy data! Use -f if you're sure." > > rm commands at all object levels and detach commands. All gave generic > > "device busy errors", > > Yes, this is a feature, not a bug. For the same reason stated above? That makes sense. Perhaps a better error message would be helpful to users in this circumstance as well. "Removing this device will destroy data permanently! Use -f if you're sure." Just some thoughts based on my own (continuing) learning curve with vinum. -Bill -- If a bird in the hand is worth two in the bush, then what can I get for two hands in the bush? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message