gvinum behaviour on disk failure

[Alastair Watts]

Hi Ulf,

Ulf Lilleengen wrote:

>>The other night we had a drive die under gvinum on FreeBSD 5.4. The 
>>setup was ad0 and ad2 in a mirror. Log messages were:
>>
>>Am I missing something (perhaps data didn't get written to ad0, but then 
>>shouldn't it have been in memory), or shouldn't gvinum have absorbed 
>>this error and supplied the data from ad0?
>>
>>Or is this a known issue/bug? I searched but couldn't find a similar 
>>reference on this list..
> 
> Could you give me the output of "gvinum printconfig"?

drive bravo device /dev/ad2s1h
drive alpha device /dev/ad0s1h
volume usr
volume tmp
volume swap
volume root
plex name usr.p1 org concat vol usr
plex name tmp.p1 org concat vol tmp
plex name swap.p1 org concat vol swap
plex name root.p1 org concat vol root
plex name usr.p0 org concat vol usr
plex name tmp.p0 org concat vol tmp
plex name swap.p0 org concat vol swap
plex name root.p0 org concat vol root
sd name usr.p1.s0 drive bravo len 75010137s driveoffset 3145993s plex 
usr.p1 plexoffset 0s
sd name tmp.p1.s0 drive bravo len 524288s driveoffset 2621705s plex 
tmp.p1 plexoffset 0s
sd name swap.p1.s0 drive bravo len 2097152s driveoffset 265s plex 
swap.p1 plexoffset 0s
sd name root.p1.s0 drive bravo len 524288s driveoffset 2097417s plex 
root.p1 plexoffset 0s
sd name usr.p0.s0 drive alpha len 75010137s driveoffset 3145993s plex 
usr.p0 plexoffset 0s
sd name tmp.p0.s0 drive alpha len 524288s driveoffset 2621705s plex 
tmp.p0 plexoffset 0s
sd name swap.p0.s0 drive alpha len 2097152s driveoffset 265s plex 
swap.p0 plexoffset 0s
sd name root.p0.s0 drive alpha len 524288s driveoffset 2097417s plex 
root.p0 plexoffset 0s

Cheers,

Al