From owner-freebsd-bugs@freebsd.org  Wed Jul 13 13:16:24 2016
Return-Path: <owner-freebsd-bugs@freebsd.org>
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 0CD7BB93FBE
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 13 Jul 2016 13:16:24 +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 EFCAA1178
 for <freebsd-bugs@FreeBSD.org>; Wed, 13 Jul 2016 13:16:23 +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 u6DDGNT2018597
 for <freebsd-bugs@FreeBSD.org>; Wed, 13 Jul 2016 13:16:23 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 13:16:24 +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: <bug-211028-8-vGXE4rgRkv@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211028-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-211028-8@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-bugs@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2016 13:16:24 -0000

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

--- Comment #8 from Dexuan Cui <decui@microsoft.com> ---
(In reply to Edward Tomasz Napierala from comment #7)
Hi Edword,
Yes, exactly.

After the disk capacity change, if I do "camcontrol reprobe da1", gpart can=
 see
 both the capacity & free space are updated.

After the disk capacity change, if first I open /dev/da1 for reading (e.g. =
dd
if=3D/dev/da1 of=3Dtmp bs=3D512 count=3D1), da driver notices "Capacity dat=
a has
changed", and gpart can see the new capacity, but the "free" space shown by
gpart is still the old. Next, "camcontrol reprobe da1" can't help and the
"free" space shown by gpart is still the old. Next, opening da1 for writing
(e.g. dd if=3D/dev/da1 of=3D/dev/da1 bs=3D512 count=3D0) can make gpart sho=
w the new
"free" space.

--=20
You are receiving this mail because:
You are the assignee for the bug.=