Date: 06 Nov 2004 22:28:36 -0700 From: secmgr <security@jim-liesl.org> To: msch@snafu.de Cc: freebsd-stable@freebsd.org Subject: Re: freebsd 5.3 have any problem with vinum ? Message-ID: <1099805316.4420.2.camel@emperor> In-Reply-To: <200411061309.11883.msch@snafu.de> References: <02f201c4ba91$f9f95db0$33017f80@psique> <20041103031316.A95136@titus.hanley.stade.co.uk> <41893F4D.6090702@jim-liesl.org> <200411061309.11883.msch@snafu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
No, I mean self corrupting raid5 sets during initialization. Discussed about 2-3 weeks ago. On Sat, 2004-11-06 at 05:09, Matthias Schuendehuette wrote: > > If you mean the 'dangling vnode'-problem with "vinum-classic": > > Try to start 'classic' vinum *after* the system has come up. Either > manually or perhaps with a script in /usr/local/etc/rc.d. This works > for me until now under 5-STABLE (a.k.a. RELENG_5).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1099805316.4420.2.camel>