Gvinum

[Ulf Lilleengen]

On Sat, Jun 16, 2007 at 05:08:49PM -0300, Giancarlo Rubio wrote:
>  Hi all
> 
>  I'm using raid 5 with 3 400gb disks, via gvinum.
> 
>  Disks
>  ad4: 381553MB <SAMSUNG HD400LJ ZZ100-14> at ata2-master SATA150
>  ad6: 381554MB <Seagate ST3400620AS 3.AAK> at ata3-master SATA150
>  ad7: 381554MB <SAMSUNG HD400LJ ZZ100-14> at ata3-slave SATA150
> 
>  When i listing the raid via gvinum show
> 
>  servidor# gvinum
>  gvinum -> list
>  3 drives:
>  D raid53                State: up       /dev/ad7s1a     A: 0/381553 MB (0%)
>  D raid52                State: up       /dev/ad6s1a     A: 0/381553 MB (0%)
>  D raid51                State: up       /dev/ad4s1a     A: 0/381552 MB (0%)
> 
>  1 volume:
>  V data                  State: up       Plexes:       1 Size:        745 GB
> 
>  1 plex:
>  P data.p0            R5 State: up       Subdisks:     3 Size:        745 GB
> 
>  3 subdisks:
>  S data.p0.s2            State: up       D: raid53       Size:        372 GB
>  S data.p0.s1            State: up       D: raid52       Size:        372 GB
>  S data.p0.s0            State: up       D: raid51       Size:        372 GB
>  gvinum ->
> 
> 
>  devfs                  1.0K    1.0K      0B   100%    /dev
>  /dev/ad0s1e            496M     14K    456M     0%    /tmp
>  /dev/ad0s1f             69G    2.0G     61G     3%    /usr
>  /dev/ad0s1d            1.4G     79M    1.2G     6%    /var
>  /dev/gvinum/data       722G    722G    -58G   109%    /home
The difference is because of the filesystem layout and metadata, while gvinum
show's you the "raw" disk data size.

When it comes to the negative numbers...I think this might have something to do
with the filesystem and not gvinum.  But perhaps you could send the output off
'gvinum printconfig'?
-- 
Ulf Lilleengen