Date: Wed, 13 Jul 2016 13:52:59 +0000 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 Message-ID: <bug-211028-8-VzUNvmxJyR@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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211028 --- Comment #10 from Andrey V. Elsukov <ae@FreeBSD.org> --- (In reply to Edward Tomasz Napierala from comment #9) > Hm. Okay. The read dd works, because the da(4) driver gets notified abo= ut > the capacity change on the first read command sent to the disk; basically > the disk responds with Unit Attention indicating this. The write dd work= s, > because it forces GEOM retaste. So it still fits the theory that GEOM > itself is fine, and it's just g_part(4) not handling it properly. As I said, tracing via dtrace or geom's internal capability should show that g_part receives resize event. In previous messages I didn't see this. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211028-8-VzUNvmxJyR>