Date: Sun, 17 Jun 2001 12:51:16 -0400 From: Bill Moran <wmoran@iowna.com> To: Drew Derbyshire <ahd@kew.com> Cc: questions@FreeBSD.ORG Subject: Re: Stopping / removing vinum segments Message-ID: <3B2CE004.5E720577@iowna.com> References: <007701c0f6de$cef773b0$94cba8c0@xena> <3B2C2B84.8792D238@iowna.com> <000801c0f72b$f25931c0$94cba8c0@xena> <3B2CC068.2A0B6C01@iowna.com> <000801c0f748$ab47a880$94cba8c0@xena>
next in thread | previous in thread | raw e-mail | index | archive | help
Drew Derbyshire wrote: > > > I'm a little confused here ... you state below that the system is idle > > and wrong. > > Understandable. > > The vinum volume was newly created. newfs had not yet been run. Therefore, > there was no data and the volume was not being used. > > The problem with resetconfig is, if I had another volume which WAS live and > active, the resetconfig would have smoked that as well. I see now. In that case you'd need to use the stop, detach, and rm commands. Some of these will need the -f switch to force the action. It can be done, I've done it. It can be difficult to get the vinum objects into a state where you can do what you want, so if I'm removing things anyway (and I don't care what happens to the data) I usually just do rm -f which will force the removal no matter what's going on. -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B2CE004.5E720577>