On Sun, Mar 11, 2001 at 12:03:34AM -0800, Matthew Jacob wrote:
>
>
> On Sun, 11 Mar 2001, Greg Lehey wrote:
>
> > On Saturday, 10 March 2001 at 17:12:42 -0800, Matt Jacob wrote:
> > > (top of tree within the last day or so):
> > >
> > > Things seem *almost* okay, but:
> > >
> > > nellie.feral.com > root vinum
> > > vinum -> stripe -v /dev/da3a /dev/da4a /dev/da5a /dev/da6a /dev/da7a /dev/da8a
> > > /dev/da9a /dev/da10a /dev/da11a /dev/da12a
> > > drive vinumdrive0 device /dev/da3a
> > > <snip>
> > > Can't get config for plex 0: Invalid argument
> > >
> > > and at the console:
> > >
> > > WARNING: Driver mistake: repeat make_dev("vinum/control")
> >
> > Hmm.
> >
> > > Mar 10 17:09:57 nellie /boot/kernel/kernel: vinumioctl: invalid ioctl from
>process 682 (vinum): c1384644
> >
> > This looks like a mismatch between the plex size in the userland and
> > kernel code. Did you rebuild vinum(8)?
>
> Complete fresh build, top of tree... I'll try again...
I'll sneak in my experience with DEVFS+vinum here as well:
vinum: loaded
vinum: reading configuration from /dev/da3s1f
vinum: updating configuration from /dev/da1s1e
vinum: updating configuration from /dev/da2s1e
vinum: updating configuration from /dev/da0s1e
swapon: adding /dev/da1s1b as swap device
swapon: adding /dev/da2s1b as swap device
Automatic boot in progress...
/dev/da0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS
/dev/da0s1a: clean, 406977 free (1049 frags, 50741 blocks, 0.2% fragmentation)
Can't stat /dev/vinum/raid01: No such file or directory
Can't stat /dev/vinum/raid01: No such file or directory
/dev/vinum/raid01: CAN'T CHECK FILE SYSTEM.
/dev/vinum/raid01: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
This was with a -current from around March 1. (don't think
anything has changed since). Booting a non-DEVFS kernel
passes the fs-check and works as expected.
/Niels Chr.
--
Niels Christian Bank-Pedersen, NCB1-RIPE.
Network Manager, Tele Danmark NET, IP-section.
"Hey, are any of you guys out there actually *using* RFC 2549?"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
