From owner-freebsd-geom@freebsd.org  Fri Sep 30 03:46:16 2016
Return-Path: <owner-freebsd-geom@freebsd.org>
Delivered-To: freebsd-geom@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id D794AC03A0C
 for <freebsd-geom@mailman.ysv.freebsd.org>;
 Fri, 30 Sep 2016 03:46:16 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id C7000C4B
 for <freebsd-geom@FreeBSD.org>; Fri, 30 Sep 2016 03:46:16 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8U3kFYT075981
 for <freebsd-geom@FreeBSD.org>; Fri, 30 Sep 2016 03:46:16 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-geom@FreeBSD.org
Subject: [Bug 211028] [GEOM][Hyper-V] gpart can't detect the new free space
 after the disk capacity changes
Date: Fri, 30 Sep 2016 03:46:16 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: commit-hook@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-211028-14739-HRsvpDeQwf@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211028-14739@https.bugs.freebsd.org/bugzilla/>
References: <bug-211028-14739@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-geom@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: GEOM-specific discussions and implementations
 <freebsd-geom.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-geom>,
 <mailto:freebsd-geom-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-geom/>
List-Post: <mailto:freebsd-geom@freebsd.org>
List-Help: <mailto:freebsd-geom-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-geom>,
 <mailto:freebsd-geom-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Sep 2016 03:46:16 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211028

--- Comment #37 from commit-hook@freebsd.org ---
A commit references this bug:

Author: ae
Date: Fri Sep 30 03:45:41 UTC 2016
New revision: 306476
URL: https://svnweb.freebsd.org/changeset/base/306476

Log:
  MFC r303019:
    Use g_resize_provider() to change the size of GEOM_DISK provider,
    when it is being opened. This should fix the possible loss of a resize
    event when disk capacity changed.

  MFC r303288:
    Do not invoke resize method if geom is being withered.

  MFC r303637:
    Do not invoke resize event if initial disk size is zero. Some disks
    report the size only after first opening.  And due to the events are
    asynchronous, some consumers can receive this event too late and
    this confuses them. This partially restores previous behaviour, and
    at the same time this should fix the problem, when already opened
    provider loses resize event.

  PR:           211028

Changes:
_U  stable/11/
  stable/11/sys/geom/geom_disk.c
  stable/11/sys/geom/geom_subr.c

--=20
You are receiving this mail because:
You are on the CC list for the bug.=