Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 25 Mar 2004 00:35:25 +0800
From:      "h0444lp6" <h0444lp6@student.hu-berlin.de>
To:        <freebsd-questions@freebsd.org>
Subject:   vinum sd length and stripesize questions
Message-ID:  <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAARzVDYFxT2kivlM5jtglkDsKAAAAQAAAAYhkDqQnIG0CKT6ZgVoGxSQEAAAAA@student.hu-berlin.de>

next in thread | raw e-mail | index | archive | help
Dear list

I have three partition of the same size on different disks (ad0, ad1 and
ad2).
In disklabel they show up as 

e:  2097152   720896    4.2BSD     2048 16384    89   # (Cyl.  715*-
2795*)

(f: ... for ad1 and ad2)

In df they show up as:

Filesystem  1K-blocks   Used  Avail Capacity  Mounted on
/dev/ad0s1e   1032142      2 949570     0%    /data0
/dev/ad1s1f   1032142      2 949570     0%    /data1
/dev/ad2s1f   1032142      2 949570     0%    /data2

MY FIRST QUESTION IS:

In the vinum configuration's sd length attribute am I to use the df
1K-block or the df Avail size? (e.g. sd length 1032142 drive ... or sd
lenth 949570 drive ...).
I am asking because Lucas writes in AbsoluteBSD df Avail, but I used
accidently 1k-block. I don't want to keep on installing and configuring
and later on run into trouble. I cross checked on Lehey's web page but
did not find any information.

MY SECOND QUESTION IS:

vinum(8) stated:

"org organization [stripesize ]
[stipesize] For type raid5, it specifies the size of a group. A group is
a portion of a plex which stores the parity bits all in the same
subdisk. It must be a factor of the plex size (in other words, the
result of dividing the plex size by the stripe size must be an integer),
and it must be a multiple of a disk sector (512 bytes)."

I understand this as stripesize has to devide sd length by ) AND 512k
has to devide stripesize by 0 is that true?

TIA

zheyu




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAARzVDYFxT2kivlM5jtglkDsKAAAAQAAAAYhkDqQnIG0CKT6ZgVoGxSQEAAAAA>