Date: Fri, 22 Jun 2001 13:21:51 +0930 From: Greg Lehey <grog@FreeBSD.org> To: Drew Derbyshire <ahd@kew.com> Cc: Bill Moran <wmoran@iowna.com>, questions@FreeBSD.ORG Subject: Re: Stopping / removing vinum segments Message-ID: <20010622132151.X57186@wantadilla.lemis.com> In-Reply-To: <002801c0fa6c$3d0f78d0$94cba8c0@xena>; from ahd@kew.com on Thu, Jun 21, 2001 at 12:07:15PM -0400 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 21 June 2001 at 12:07:15 -0400, Drew Derbyshire wrote: > On Monday, June 18, 2001 9:53 PM, Greg Lehey <grog@FreeBSD.org> wrote: >> On Sunday, 17 June 2001 at 12:15:04 -0400, Drew Derbyshire wrote: >>> On Sunday, June 17, 2001 10:36 AM, Bill Moran <wmoran@iowna.com> 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. >> >> So what was wrong about it? > > The original layout had two drives, one volume, four plexes, eight > subdisks. I actually wanted four volumes, two plexes with one subdisk on > each disk per volume. OK, so not wrong, just undesired. >>> 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. > > I know I shouldn't use resetconfig. But I couldn't use rm either, > because I couldn't shutdown the items I wanted to rm. I refused to > use force because it should not have been needed on a clean > configuration. "I refused to use the tools provided, and now I can't get the work done". 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. >> So what did you want to do? What did try? What didn't work? > > rm commands at all object levels and detach commands. All gave generic > "device busy errors", Yes, this is a feature, not a bug. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers 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?20010622132151.X57186>