Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 23 Nov 2009 09:43:15 -0600
From:      Peter Steele <psteele@maxiscale.com>
To:        "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   gmirror creation problem in 8.0
Message-ID:  <7B9397B189EB6E46A5EE7B4C8A4BB7CB33AEBD53@MBX03.exg5.exghost.com>

next in thread | raw e-mail | index | archive | help
I have a script that configures a mirrored file system and have been using =
this successfully in 7.0 without any issues. The commands I use to set up t=
he mirror are:

gmirror label -v -n -b round-robin gm0 ad4s1
gmirror configure -a gm0

This never gave me any trouble in 7.0, but in 8.0 the configure command iss=
ues the following error:

gmirror: Missing priority argument

My initial assumption was that the gmirror command has a new argument that =
has to be included now to set a priority value but the man page doesn't sho=
w any such argument. The gmirror insert command *does* have a "-p" option t=
o set a priority value for a member being added to the mirror, but this is =
the same as in 7.0.

The missing argument error appears to be only a warning of sorts, since it =
does create the gmirror device. However, when I insert a second drive, it d=
oes not autosync, and a dump of the mirror reveals why:

# gmirror list
Geom name: gm0
State: DEGRADED
Components: 2
Balance: round-robin
Flags: NOAUTOSYNC
Providers:
1. Name: mirror/gm0
   Mediasize: 18253766656 (17G)
Consumers:
1. Name: ad4s1
   Mediasize: 18253767168 (17G)
   State: ACTIVE
   Priority: 0
   Flags: NONE
2. Name: ad5s1
   Mediasize: 18253767168 (17G)
   State: STALE
  Priority: 1
   Flags: SYNCHRONIZING

For some reason the mirror is created in NOAUTOSYNC mode, even though the -=
a option is included in the configure command. I have to issue a manual reb=
uild to get the new member to start synchronizing. The system logs also hav=
e some interesting messages during a reboot:

Nov 23 13:45:43  kernel: GEOM: ad4s1: geometry does not match label (255h,6=
3s !=3D 16h,63s).
Nov 23 13:45:43  kernel: GEOM: ad4s1: media size does not match label.
Nov 23 13:45:44  kernel: GEOM: ad5s1: geometry does not match label (255h,6=
3s !=3D 16h,63s).
Nov 23 13:45:44  kernel: GEOM: ad5s1: media size does not match label.

This is again something I have not seen in 7.0.

Does anyone have any comments on this? I am using RC3 so perhaps this is a =
known issue.




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