Date: 01 Apr 2001 21:49:22 -0500 From: Kirk Strauser <kirk@strauser.com> To: freebsd-fs@freebsd.org Subject: Re: My Vinum heart attack Message-ID: <87r8zcm2x9.fsf@pooh.honeypot> In-Reply-To: <20010402120212.D25226@wantadilla.lemis.com> References: <87vgooi7kz.fsf@pooh.honeypot> <20010402082816.J77617@wantadilla.lemis.com> <87g0fsi1i2.fsf@pooh.honeypot> <20010402102211.B25226@wantadilla.lemis.com> <871yrcnijq.fsf@pooh.honeypot> <20010402120212.D25226@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 2001-04-02T02:32:13Z, Greg Lehey <grog@lemis.com> writes:
> > Can't create /dev/vinum/: File exists
> > Can't create /dev/vinum/vol/: File exists
> This looks very old. Which version of vinum(8) is this?
I don't have access to the exact date of the build, but it was circa
2001-02-11.
> Ah. Yes, you can't do that. You *must* have your kernel and userland in
> sync.
Fair enough, but that was my original problem: following the update
instructions in /usr/src/UPDATING could have left me with a broken system.
Nowhere have I read anything warning users to keep them in rigid lockstep.
I mean, it's understood that you don't want your kernel and userland to be
too far out of sync, but I wasn't aware that it was that critical.
For example, here's an entry from UPDATING:
20010109:
ipfw interface changed. Make sure that the userland and kernel match
or you won't have the firewall rules you think you do.
The instant I read that, I knew to watch out for the two parts. I had no
idea that Vinum also had such conditions.
Two quick side questions:
How do you pronounce `Vinum'?
Did you ever get to look at my Vinum-on-IDE post from a month ago?
--
Kirk Strauser
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87r8zcm2x9.fsf>