Hand on gmirror (Was: Re: gmirror bugs, how many?)

João Carlos Mendes Luís jonny at jonny.eng.br
Mon Nov 29 13:27:54 PST 2004


I finally got the system to boot with gmirror fully enabled.  But I got 
this during boot:


GEOM_MIRROR: Device vol0 created (id=3592859320).
GEOM_MIRROR: Device vol0: provider ad0s1 detected.
GEOM_MIRROR: Device vol0: provider ad1s1 detected.
GEOM_MIRROR: Device vol0: provider ad1s1 activated.
GEOM_MIRROR: Cannot update metadata on disk ad0s1 (error=1).
GEOM_MIRROR: Device vol0: provider ad0s1 activated.
GEOM_MIRROR: Device vol0: provider mirror/vol0 launched.
GEOM_MIRROR: Cannot update metadata on disk ad0s1 (error=1).
GEOM_MIRROR: Device vol0: provider ad0s1 disconnected.

Both slices have been created with a cylinder less than the maximum, to 
avoid having to use hardcoded names.

The last messages before the shutdown -r were:


Nov 29 15:03:56 sigesc kernel: GEOM: Configure ad0s1a, start 0 length 
536870912 end 536870911
Nov 29 15:03:56 sigesc kernel: GEOM: Configure ad0s1b, start 536870912 
length 536870912 end 1073741823
Nov 29 15:03:56 sigesc kernel: GEOM: Configure ad0s1c, start 0 length 
8447394304 end 8447394303
Nov 29 15:03:56 sigesc kernel: GEOM: Configure ad0s1d, start 1073741824 
length 7373652480 end 8447394303
Nov 29 15:04:16 sigesc kernel: GEOM_MIRROR: Device vol0: provider ad0s1 
detected.
Nov 29 15:04:16 sigesc kernel: GEOM_MIRROR: Device vol0: rebuilding 
provider ad0s1.
Nov 29 15:35:19 sigesc kernel: GEOM_MIRROR: Device vol0: rebuilding 
provider ad0s1 finished.
Nov 29 15:35:19 sigesc kernel: GEOM_MIRROR: Device vol0: provider ad0s1 
activated.
Nov 29 15:35:19 sigesc kernel: GEOM: Configure ad0s1a, start 0 length 
536870912 end 536870911
Nov 29 15:35:19 sigesc kernel: GEOM: Configure ad0s1b, start 536870912 
length 536870912 end 1073741823
Nov 29 15:35:19 sigesc kernel: GEOM: Configure ad0s1c, start 0 length 
8447394304 end 8447394303
Nov 29 15:35:19 sigesc kernel: GEOM: Configure ad0s1d, start 1073741824 
length 7373652480 end 8447394303


I thought the syncronization was completed without errors.  What have I 
missed?


More information about the freebsd-hackers mailing list