Date: Tue, 18 Jan 2011 17:57:47 +0100 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-hackers@freebsd.org Subject: Re: gpart/gstripe problems? Message-ID: <ih4gqa$faq$1@dough.gmane.org> In-Reply-To: <E1PfDnN-000BsP-9P@kabab.cs.huji.ac.il> References: <E1PfDnN-000BsP-9P@kabab.cs.huji.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18.1.2011 16:48, Daniel Braniss wrote:
> I have:
> sf-03> gpart show
> => 34 976773101 ada0 GPT (466G)
> 34 128 1 freebsd-boot (64K)
> 162 4194304 2 freebsd-ufs (2.0G)
> 4194466 100663296 3 freebsd-swap (48G)
> 104857762 871915373 4 freebsd (416G)
>
> => 34 976773101 ada1 GPT (466G)
> 34 128 1 freebsd-boot (64K)
> 162 4194304 2 freebsd-ufs (2.0G)
> 4194466 100663296 3 freebsd-swap (48G)
> 104857762 871915373 4 freebsd (416G)
>
> sf-03> ls -ls /dev/ada*
> 0 crw-r----- 1 root operator 0, 78 Jan 18 14:35 /dev/ada0
> 0 crw-r----- 1 root operator 0, 80 Jan 18 14:35 /dev/ada0p1
> 0 crw-r----- 1 root operator 0, 81 Jan 18 14:35 /dev/ada0p2
> 0 crw-r----- 1 root operator 0, 82 Jan 18 14:35 /dev/ada0p3
> 0 crw-r----- 1 root operator 0, 83 Jan 18 14:35 /dev/ada0s4
> 0 crw-r----- 1 root operator 0, 79 Jan 18 14:35 /dev/ada1
> 0 crw-r----- 1 root operator 0, 84 Jan 18 14:35 /dev/ada1p1
> 0 crw-r----- 1 root operator 0, 85 Jan 18 14:35 /dev/ada1p2
> 0 crw-r----- 1 root operator 0, 86 Jan 18 14:35 /dev/ada1p3
> 0 crw-r----- 1 root operator 0, 87 Jan 18 14:35 /dev/ada1s4
>
> next I did:
> # gstripe label s0 /dev/ada{0,1}s4
> and on the console the following appeared:
> GEOM_STRIPE: Device s0 activated.
> GEOM_STRIPE: Cannot add disk gptid/bd0f6e54-22ea-11e0-b27c-001b245d5a5b to s0
> (error=17).
> GEOM_STRIPE: Cannot add disk gptid/bdf7d563-22ea-11e0-b27c-001b245d5a5b to s0
> (error=17).
>
> is this realy an error?
It looks like a similar type of error as people commonly see with
gmirror - a race with glabel. If you don't use glabel, the easyest way
would be to disable some of kern.geom.label.*.
I think one way to solve it would be for glabel export an attribute for
devices (providers) on which this is possible (i.e. those whose size
doesn't change from the underlying devices) which could be checked by
such GEOM classes.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ih4gqa$faq$1>