is vinum in current working for anyone
ticso at cicely12.cicely.de
Tue Jan 6 04:11:18 PST 2004
On Tue, Jan 06, 2004 at 12:41:12PM +0100, Alexander Leidinger wrote:
> On Tue, 6 Jan 2004 12:24:33 +1030
> "Greg 'groggy' Lehey" <grog at freebsd.org> wrote:
> > On Monday, 5 January 2004 at 11:51:06 -0500, Stephen Corbesero wrote:
> > >
> > > I have been unable to use vinum in current since about 5.1. I have
> > > just sent debugging information to Greg Lehey, but I was wondering
> > > if it is working for anyone and how our configurations differ.
> > >
> > > If rc.conf specifies vinum_start="YES", my system usually crashes as
> > > soon as vinum loads and starts scanning disks. Sometimes it doesn't
> > > crash, but the vinum config is lost on at least one of the vinum
> > > drives.
> > Yes, I have your backtrace, and I've been trying to make sense of it.
> > In the meantime I've had another one; together they give me the
> > feeling that something has gone funny just recently. I don't
> > understand from the backtrace how anything should have got trashed on
> > disk, though; I suspect that the data really was still there, and a
> > (the) bug gave the impression that it wasn't.
> FYI: I've a SATA system, which tells me the volume, plexe and subdisks
> are crashed on every boot. When I just do a "setstate up" I can fsck and
> use the volume just fine. It runs with an icc comiled kernel ATM, but I
> see the same behavior with a gcc compiled kernel. I also get spurious
> interrupts at a shutdown and I think this is the reason of this failure
> after booting the system... Am I right or should I try to dig into this?
You should try a manual saveconfig after getting everything up.
vinum should tell you whenever it sees a reason for taking anything
down - unless your shutdown includes such vinum messages I don't think
that there is any relation.
B.Walter BWCT http://www.bwct.de
ticso at bwct.de info at bwct.de
More information about the freebsd-current