Greg Lehey wrote:
>
> On Tuesday, 21 March 2000 at 14:48:55 +0100, Palle Girgensohn wrote:
> > Hi!
> >
> > I'm having a strange problem after upgrading: There are no raw
> > devices created for vinum volumes.
>
> Indeed there are. You list them below. There are no longer any block
> devices.
>
At 6:59 PM +0100 2000/3/21, Palle Girgensohn wrote:
> I did some rtfm and src digging, it appears the listing I gave is
> correct; the raw devices are in the rvinum dircetory.
How did you get an /dev/rvinum? I don't have one
--
These are my opinions -- not to be taken as offic
This fixes it for me. Is my installation faulty, or is this
something that vinum fails to do when creating its devices?
#! /bin/sh
cd /dev/vinum
for i in ../rvinum/*; do ln -s $i r`basename $i`; done
/Palle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in t
Hello again.
I did some rtfm and src digging, it appears the listing I gave is
correct; the raw devices are in the rvinum dircetory. Problem is,
dump looks in vinum/r*. There seems that vinum introduces a bug
here, since dump's rawname function replaces the last '/' in the
device name with '/r'.
On Tuesday, 21 March 2000 at 14:48:55 +0100, Palle Girgensohn wrote:
> Hi!
>
> I'm having a strange problem after upgrading: There are no raw
> devices created for vinum volumes.
Indeed there are. You list them below. There are no longer any block
devices.
> This makes dump(8) puke.
>
> This i
Hi!
I'm having a strange problem after upgrading: There are no raw
devices created for vinum volumes. This makes dump(8) puke.
This is a 3.4 system:
ls -laF /dev/vinum
...
crwxr-xr-- 1 root wheel 91, 1 2 Jul 1999 rusr*
drwxr-xr-x 2 root wheel 512 2 Jul 1999 rvol/
...
brwxr-xr