Encrypting raid5 volume with geli

[Rick C. Petty]

On Thu, Dec 11, 2008 at 11:38:56PM +0100, oxy wrote:
> here it is:
> 
> [root at test /]# gvinum l
> 4 drives:
> D disk_2                State: up       /dev/ad9        A: 0/238475 MB (0%)
> D disk_1                State: up       /dev/ad8        A: 0/238475 MB (0%)
> D disk_4                State: up       /dev/ad5        A: 0/238475 MB (0%)
> D disk_3                State: up       /dev/ad4        A: 0/238475 MB (0%)
> 
> 1 volume:
> V raid5                 State: down     Plexes:       1 Size:        698 GB
> 
> 1 plex:
> P raid5.p0           R5 State: down     Subdisks:     4 Size:        698 GB
> 
> 4 subdisks:
> S raid5.p0.s0           State: stale    D: disk_1       Size:        232 GB
> S raid5.p0.s1           State: stale    D: disk_2       Size:        232 GB
> S raid5.p0.s2           State: stale    D: disk_3       Size:        232 GB
> S raid5.p0.s3           State: stale    D: disk_4       Size:        232 GB
> 
> [root at test /]# geli init -P -K /root/raid5.key /dev/gvinum/raid5
> geli: Cannot store metadata on /dev/gvinum/raid5: Device not configured.

The error message is quite accurate-- the raid5 volume is down because the
plex is stale.  You need to run a "gvinum start raid5.p0" and let it
complete before the volume will be "up".  This operation will sync the four
plexes and write out the parity info.

There are a set of patches that lulf@ has which I believe put the volume in
"up" state initially instead of "down", but maybe it only works for
mirrors.  The code in current and RELENG_7 does initially put the volume in
"down" state.

-- Rick C. Petty