Gvinum

[Ulf Lilleengen]

On søn, jun 17, 2007 at 02:29:09pm +0000, Giancarlo Rubio wrote:
> > 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'?
> 
>  gvinum -> printconfig
>  # Vinum configuration of servidor.AERO, saved at Sun Jun 17 11:28:31 2007
>  drive raid53 device /dev/ad7s1a
>  drive raid52 device /dev/ad6s1a
>  drive raid51 device /dev/ad4s1a
>  volume data
>  plex name data.p0 org raid5 388s vol data
>  sd name data.p0.s2 drive raid53 len 781422300s driveoffset 265s plex
>  data.p0 plexoffset 776s
>  sd name data.p0.s1 drive raid52 len 781422300s driveoffset 265s plex
>  data.p0 plexoffset 388s
>  sd name data.p0.s0 drive raid51 len 781419196s driveoffset 265s plex
>  data.p0 plexoffset 0s
>  gvinum ->

Well, seems ok. Everything works fine, right? Perhaps just a bug in 'df'. 

Btw, it's not recommended to have different sized subdisk in the array.
-- 
Ulf Lilleengen