Date: Thu, 11 Oct 2007 11:34:20 +0200 From: "Ivan Voras" <ivoras@freebsd.org> To: "Eric Anderson" <anderson@freebsd.org> Cc: John Nielsen <lists@jnielsen.net>, freebsd-geom@freebsd.org Subject: Re: removing / replacing in-use components in gvirstor Message-ID: <9bbcef730710110234i64f35d49gf6bb0d39067d03d1@mail.gmail.com> In-Reply-To: <470D7E5F.4020607@freebsd.org> References: <200710101817.56082.lists@jnielsen.net> <470D7E5F.4020607@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/10/2007, Eric Anderson <anderson@freebsd.org> wrote: > > In thinking about how I personally would use it, I realized I would add > > drives to a system until I ran out of slots or controller connections, and > > then want to upgrade to larger drives. From the manpage (and the code) it > > doesn't look like this is currently possible unless the drive you want to > > replace happens to be unused. How feasible would it be to either extend > > the "remove" verb to migrate in-use chunks to other (existing) providers or > > create a "replace" verb to migrate in-use chunks to a new provider? > > I wonder if making each drive a member of a single-device mirror, and > then including all the mirrors into the gvirstor GEOM would do the > trick. That way, you can simply add a new drive to the mirrorset you > want to replace, let the mirror sync, and then pop the old drive out. I > think the only remaining step is to re-mirror the mirror, or extend the > mirror or partition.. I plan to add offline drive-replacing verb to the userland utility but yes, that would also work.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9bbcef730710110234i64f35d49gf6bb0d39067d03d1>