Date: Tue, 12 Jul 2016 09:32:25 +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@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211028 Bug ID: 211028 Summary: [GEOM][Hyper-V] gpart can't detect the new free space after the disk capacity changes Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: decui@microsoft.com When testing Hyper-V's Online VHDX Resize feature (refer to Bug 211000), I noticed an issue: after resizing =E2=80=9Cda1=E2=80=9D, if there was a disk= read before "camcontrol reprobe da1", gpart couldn't detect the new =E2=80=9Cfree space= ", though it could detect the new disk capacity. To reproduce the bug, we need to run FreeBSD 12-CURRENT guest on Hyper-V (we need to make sure the 2 patches mentioned by https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211000#c4 are used to a= void the known issues) and do the following 1. This is before the disk capacity change: [root@decui-b11 ~]# gpart show da1 =3D> 63 83886017 da1 MBR (40G) 63 83886017 - free - (40G) 2. Expand the disk capacity from 40GB to 50GB by Hyper-V management tool. 3.=20 [root@decui-b11 ~]# dd if=3D/dev/da1 of=3D/dev/null bs=3D512 count=3D1 1+0 records in 1+0 records out 512 bytes transferred in 0.000715 secs (715864 bytes/sec) [root@decui-b11 ~]# gpart show da1 =3D> 63 83886017 da1 MBR (50G) 63 83886017 - free - (40G) We can see the 'free' space can't grow to 50GB. 4. This can't help: [root@decui-b11 ~]# camcontrol reprobe da1 [root@decui-b11 ~]# gpart show da1 =3D> 63 83886017 da1 MBR (50G) 63 83886017 - free - (40G) --=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>