Date: Wed, 13 Jul 2016 13:16:24 +0000 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 Message-ID: <bug-211028-14739-sZ2SFC7gM7@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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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 on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211028-14739-sZ2SFC7gM7>