Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 03 Oct 2012 17:35:59 +0300
From:      Andriy Gapon <avg@FreeBSD.org>
To:        Steven Hartland <killing@multiplay.co.uk>
Cc:        freebsd-fs@FreeBSD.org, freebsd-geom@FreeBSD.org
Subject:   Re: zfs zvol: set geom mediasize right at creation time
Message-ID:  <506C4D4F.2090909@FreeBSD.org>
In-Reply-To: <80F518854AE34A759D9441AE1A60D2DC@multiplay.co.uk>
References:  <505DF1A3.1020809@FreeBSD.org> <80F518854AE34A759D9441AE1A60D2DC@multiplay.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
on 23/09/2012 04:04 Steven Hartland said the following:
> Do you know what the effect of the volblocksize change
> will have on a volume who's disk block size changes?
> e.g. via a quirk for a 4k disk being added

I am not sure that I got your question...
My patch doesn't affect neither volblocksize value nor disk block size [geom
property].
It changes only stripe size geom property.

> I ask as we've testing a patch here which changes ashift to
> be based on stripesize instead of sectorsize but in its
> current form it has some odd side effects on pools which
> are boot pools.
> 
> Said patch is attached for reference.

I think that the patch makes sense and would be curious to learn more about the
side-effects.

-- 
Andriy Gapon



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