gmirror weird behaviour

Pawel Jakub Dawidek pjd at FreeBSD.org
Fri Oct 26 00:58:23 PDT 2007


On Fri, Oct 26, 2007 at 12:02:40AM +0200, Mario Pranjic wrote:
> Hi!
> 
> I have a system with 2 250 GB disks in mirror:
> [root at haerbe ~]# gmirror status
>       Name    Status  Components
> mirror/gmo  COMPLETE  ad0
>                       ad2
> 
> 
> system info:
> FreeBSD haerbe.net 6.2-RELEASE-p7 FreeBSD 6.2-RELEASE-p7 #0: Wed Sep  5
> 06:24:11 CEST 2007     root at haerbe.net:/usr/obj/usr/src/sys/HAERBE  i386
> 
> 
> At some point ad0 disk was detached from the system:
> Oct 25 06:43:10 haerbe ad0: FAILURE - device detached
> Oct 25 06:43:10 haerbe subdisk0: detached
> Oct 25 06:43:10 haerbe ad0: detached
> Oct 25 06:43:10 haerbe GEOM_MIRROR: Device gmo: provider ad0 disconnected.
> Oct 25 06:43:10 haerbe g_vfs_done():mirror/gmos2e[READ(offset=10598187008,
> length=16384)]error = 6
> Oct 25 06:43:10 haerbe g_vfs_done():mirror/gmos2e[READ(offset=30252744704,
> length=16384)]error = 6
> 
> Mirror status:
> [root at haerbe /www/_backups/hrbwiki/2007-10-22]# gmirror status
>       Name    Status  Components
> mirror/gmo  DEGRADED  ad2
> [root at haerbe /www/_backups/hrbwiki/2007-10-22]# gmirror list
> Geom name: gmo
> State: DEGRADED
> Components: 2
> Balance: round-robin
> Slice: 4096
> Flags: NONE
> GenID: 0
> SyncID: 2
> ID: 3221909623
> Providers:
> 1. Name: mirror/gmo
>    Mediasize: 250059349504 (233G)
>    Sectorsize: 512
>    Mode: r8w8e10
> Consumers:
> 1. Name: ad2
>    Mediasize: 250059350016 (233G)
>    Sectorsize: 512
>    Mode: r1w1e1
>    State: ACTIVE
>    Priority: 0
>    Flags: NONE
>    GenID: 0
>    SyncID: 2
>    ID: 1951693847
> 
> 
> I cleaned the mirror:
> [root at haerbe]# gmirror forget gmo
> 
> [root at haerbe ~]# gmirror status
>       Name    Status  Components
> mirror/gmo  COMPLETE  ad2
> 
> 
> After reboot the system is aware of both disks:
> ad0: 238475MB <Seagate ST3250820A 3.AAE> at ata0-master UDMA100
> ad2: 238475MB <Seagate ST3250820A 3.AAE> at ata1-master UDMA100
> 
> 
> but after that:
> GEOM_MIRROR: Cannot add disk ad2 to gmo (error=22).
> Root mount waiting for: GMIRROR
> Root mount waiting for: GMIRROR
> Root mount waiting for: GMIRROR
> GEOM_MIRROR: Force device gmo start due to timeout.
> GEOM_MIRROR: Device gmo: provider ad0 activated.
> GEOM_MIRROR: Device gmo: provider mirror/gmo launched.
> 
> And the system rebooted with ad0 in mirror and not ad2!
> [root at haerbe ~]# gmirror list
> Geom name: gmo
> State: DEGRADED
> Components: 2
> Balance: round-robin
> Slice: 4096
> Flags: NONE
> GenID: 0
> SyncID: 2
> ID: 3221909623
> Providers:
> 1. Name: mirror/gmo
>    Mediasize: 250059349504 (233G)
>    Sectorsize: 512
>    Mode: r8w8e10
> Consumers:
> 1. Name: ad0
>    Mediasize: 250059350016 (233G)
>    Sectorsize: 512
>    Mode: r1w1e1
>    State: ACTIVE
>    Priority: 0
>    Flags: DIRTY
>    GenID: 0
>    SyncID: 2
>    ID: 2195860303
> 
> [root at haerbe ~]# gmirror status
>       Name    Status  Components
> mirror/gmo  DEGRADED  ad0
> 
> 
> Now I synced mirror again successfuly but this is weird. It should not be
> happening.
> 
> Any ideas what is going on?

No idea, but in the future could you add kern.geom.mirror.debug=1 to
your /boot/loader.conf? This will tell us why you get EINVAL when
gmirror tries to attach a disk.

-- 
Pawel Jakub Dawidek                       http://www.wheel.pl
pjd at FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-geom/attachments/20071026/22c9500b/attachment.pgp


More information about the freebsd-geom mailing list