From owner-freebsd-bugs@freebsd.org Wed Jul 13 11:49:59 2016 Return-Path: Delivered-To: freebsd-bugs@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 20680B97DC1 for ; Wed, 13 Jul 2016 11:49:59 +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 0FF0C1BE6 for ; Wed, 13 Jul 2016 11:49:59 +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 u6DBnw5T026247 for ; Wed, 13 Jul 2016 11:49:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 211028] [GEOM][Hyper-V] gpart can't detect the new free space after the disk capacity changes Date: Wed, 13 Jul 2016 11:49:58 +0000 X-Bugzilla-Reason: AssignedTo 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: decui@microsoft.com 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: In-Reply-To: References: 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-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2016 11:49:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211028 --- Comment #5 from Dexuan Cui --- (In reply to Andrey V. Elsukov from comment #3) Thank you Andrey for the detailed instructions! g_resize_provider() returns at Line 671 and at this line, both 'size' and 'pp->mediasize' are the new disk capacity! This is pretty strange, because = at this time pp->mediasize is supposed to be the old disk capacity. I'm trying= to find out why this happens. 661 void 662 g_resize_provider(struct g_provider *pp, off_t size) 663 { 664 struct g_hh00 *hh; 665 666 G_VALID_PROVIDER(pp); 667 if (pp->flags & G_PF_WITHER) 668 return; 669 670 if (size =3D=3D pp->mediasize) 671 return; 672 673 hh =3D g_malloc(sizeof *hh, M_WAITOK | M_ZERO); 674 hh->pp =3D pp; 675 hh->size =3D size; 676 g_post_event(g_resize_provider_event, hh, M_WAITOK, NULL); 677 } --=20 You are receiving this mail because: You are the assignee for the bug.=