Date: Tue, 12 Jul 2016 12:03:00 +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-vs4TVVPeXn@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=211028 Andrey V. Elsukov <ae@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ae@FreeBSD.org --- Comment #3 from Andrey V. Elsukov <ae@FreeBSD.org> --- So, disk provider has changed its size, I assume `camcontrol reprobe` has initiated g_disk_resize event. How it should work in my understanding: 1. `camcontrol reprobe` triggers calling of disk_resize() 2. disk_resize() calls g_disk_resize() event 3. GPART class receives resize event, g_part_resize() should be called 4. GPART_MBR's method g_part_mbr_resize() should be called 5. "GEOM_PART: da1 was automatically resized. Use `gpart commit da1` to save changes or `gpart undo da1` to revert them." message should be printed in the console. If you don't see the message from p.5 - something doesn't work as expected. You can use the following dtrace command to debug: # kldload dtraceall # dtrace -n 'dtrace -n 'fbt::*disk_resize:entry fbt::g_part_*resize:entry {stack(5);}' -- 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-vs4TVVPeXn>