VINUM doesn`t work

VINUM doesn`t work

Post by Raffaell Moscatiell » Sat, 29 Apr 2000 04:00:00



Vinum, the software raid for free-bsd version for 4.0 does not work. I
have vinum configured
as starting at boot-time with start_vinum = "YES". Also I can use
vinumlike vinum create config1.
Config1 is a file, that contains
drive a device /dev/da1s1e
volume myvol
plex org concat
sd lenght 32m drive a
The system response is
1: drive a device /dev/da1s1e
** 1 : Invalid argument
   4: sd lenght 32m drive a
** 4 : invalid keyword: lenght: Invalid argument
0 drives:
1 volumes:
V myvol                 State: up       Plexes:       1 Size:
0  B

1 plexes:
P myvol.p0            C State: up       Subdisks:     0 Size:
0  B

0 subdisks:

The result is: vinum creates something but does not allocate memory, so
that i can
not make a filesystem and mount them.
And don`t talk me that /dev/da1s1e does not exist. It exist and is a
functionally partition,
with mount you see :
/dev/da0s1a on / (ufs, local, writes: sync 159 async 285, reads: sync
257 async 9)
/dev/da1s1e on /d11 (ufs, local, writes: sync 2 async 0, reads: sync 1
async 0)
/dev/da1s2e on /d12 (ufs, local, writes: sync 2 async 0, reads: sync 1
async 0)
/dev/da1s3e on /d13 (ufs, local, writes: sync 2 async 0, reads: sync 1
async 0)
/dev/da1s4e on /d14 (ufs, local, writes: sync 2 async 0, reads: sync 1
async 0)
/dev/da0s2e on /usr (ufs, local, writes: sync 9 async 146, reads: sync
218 async 20)
/dev/da0s3e on /var (ufs, local, writes: sync 129 async 337, reads: sync
39 async 0)
procfs on /proc (procfs, local)

 
 
 

VINUM doesn`t work

Post by Vallo Kallast » Sat, 29 Apr 2000 04:00:00



> Vinum, the software raid for free-bsd version for 4.0 does not work. I
> have vinum configured
> as starting at boot-time with start_vinum = "YES". Also I can use
> vinumlike vinum create config1.
> Config1 is a file, that contains
> drive a device /dev/da1s1e
> volume myvol
> plex org concat
> sd lenght 32m drive a
> The system response is
> 1: drive a device /dev/da1s1e
> ** 1 : Invalid argument
>    4: sd lenght 32m drive a
> ** 4 : invalid keyword: lenght: Invalid argument
                         ^^^^^^^^
> 0 drives:
> 1 volumes:
> V myvol                 State: up       Plexes:       1 Size:
> 0  B
> 1 plexes:
> P myvol.p0            C State: up       Subdisks:     0 Size:
> 0  B

No such keyword as "lenght" exist. Your native language isn't english,
aren't you? :-)
I've got this for innumerable times now... as my native language isn't
english as well, hehe.
--

Vallo Kallaste


 
 
 

1. WHY->Vinum drives "auto" down hrs after ->vinum start

Greetings Again,

Under 4.1-release, I'm running Raid5 with 3 drives and after bootup, I
normally do a........
    vinum start
    mount /dev/vinum/raid /raid
and all appears well.

But after some period of time [hrs] , if I do a ........
    vinum list
I see that the 3 drives are all marked as down, but volumes, plexes and
subdisks are all still up.

But if I do a.......
    umount /raid
    vinum stop
    vinum start
    mount /dev/vinum/raid /raid
all seems to be OK again, when I........
    vinum list

What's going on here ?

Appreciatively,
Courtney

2. LINUXWORLD: IBM'S MILLS SEES LINUX IN 'NEW ERA'

3. net doesn`t work after kernel recompile

4. Problem with LILO in RH 5.2

5. Crondeamon doesn`t work

6. Problem Upgrading to NCSA HTTPd 1.5a

7. color-ls doesn`t work

8. 2.4 NFS server/client performance

9. Mouse doesn`t work in textmode

10. ATI Ultra Pro: Interlacing doesn`t work

11. xterm -e doesn`t work

12. Mouse doesn`t work in textmode