Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 1 Mar 2017 19:13:17 +0200
From:      Andriy Gapon <avg@FreeBSD.org>
To:        "Andrey V. Elsukov" <ae@FreeBSD.org>, freebsd-geom@FreeBSD.org
Subject:   Re: GEOM_PART: zvol/pond/xxx was automatically resized, every boot
Message-ID:  <16315780-6525-d1ce-1129-6f9307155649@FreeBSD.org>
In-Reply-To: <49828d0f-fe1c-f635-82c7-b63a32b6bba9@FreeBSD.org>
References:  <cfbca2ca-57ec-2b49-b99e-2df794254b46@FreeBSD.org> <49828d0f-fe1c-f635-82c7-b63a32b6bba9@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 28/02/2017 14:05, Andrey V. Elsukov wrote:
> On 28.02.2017 13:00, Andriy Gapon wrote:
>> This is quite annoying as I have to do gpart commit after each reboot to make my
>> zvols usable.
>>
>> To add some data:
>>> gpart show zvol/pond/raidz0
>> =>      63  10485697  zvol/pond/raidz0  MBR  (5.0G)
>>         63  10485697                    - free -  (5.0G)
>>
>> The zvol actually has whole-disk ZFS on it, which uses zfsboot for booting.
>> In other words, the first block of the zvol is the first block of zfsboot binary.
> 
> Hi Andriy,
> 
> I think the attached (untested) patch can help.


The patch does help.
Thank you very much!

-- 
Andriy Gapon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16315780-6525-d1ce-1129-6f9307155649>