Date: Wed, 8 Feb 2006 10:20:13 +1030 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Lukas Ertl <le@FreeBSD.org> Cc: Ferruccio Zamuner <nonsolosoft@diff.org>, freebsd-geom@FreeBSD.org Subject: Re: gvinum setstate failure Message-ID: <20060207235013.GJ855@wantadilla.lemis.com> In-Reply-To: <20060207110028.U3500@pcle2.cc.univie.ac.at> References: <43E86E6E.1030200@diff.org> <20060207110028.U3500@pcle2.cc.univie.ac.at>
next in thread | previous in thread | raw e-mail | index | archive | help
--k6SrlR5F+BMzH45x Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tuesday, 7 February 2006 at 11:01:14 +0100, Lukas Ertl wrote: > On Tue, 7 Feb 2006, Ferruccio Zamuner wrote: > >> While I'm able to execute from gvinum >> gvinum -> setstate up veloce.p0.s0 >> >> The same command on sicuro.p0.s0 fails: >> gvinum -> setstate up sicuro.p0.s0 >> gvinum: cannot set subdisk state >> >> gvinum -> setstate up sicuro.p1.s0 >> gvinum: cannot set subdisk state >> >> sicuro is the name of volume in mirror, while veloce is in stripping. >> >> How can I change stale status to up on those subdisks? > > If it's a mirror you should run "start <volume>" to let it synchronize. 'setstate' is not the same as 'start'. It's an emergency function to manipulate the state without going through the normal procedures. For example, if you know that the plex currently marked 'up' is in fact corrupt, and the plex currently marked 'down' contains the correct data, you don't want to run start. Greg -- See complete headers for address and phone numbers. --k6SrlR5F+BMzH45x Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFD6TI1IubykFB6QiMRAncGAKCJw3dza1i7Z7nnrw9SGGPo2kICNQCeMPxd dF/4roqjTl1o+CwI/WeiaEE= =Xzon -----END PGP SIGNATURE----- --k6SrlR5F+BMzH45x--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060207235013.GJ855>