This is a known issue. LDOMs doesn't support dynamic resizing of I/O devices (volumes included). Even if you run "prtvtoc" on that disk corresponding to that volume in the guest, you will see that it does not show the new size. The SUN bug id for this is: CR 6699271 Dynamic virtual disk size management.
Till this is fixed, the workaround is to stop and restart the guest. I think in 1.0.2 it just happened to work by chance for single slice volumes, the code for this support is not yet in, someone from the LDOMs engineering can confirm. Regards, Misha. On Thu, Jul 10, 2008 at 1:06 PM, Brian Wroblewski <brian.wroblewski at we-energies.com> wrote: > I am having problems growing a filesystem in a logical domain after growing > the volume in the control domain. We are using LDoms 1.0.3 and Veritas > Storage Foundation 5.0 MP1 installed on both the control domain and on the > logical domain. I ran the vxassist in the control domain to grow the volume > and then I try to run the fsadm command in the logical domain to grow the > filesystem but I get an error saying that I cannot expand more then the size > of the underlying device. > > Vxprint on the control domain shows the new volume size, but the error > message from the fsadm command shows the old size. If I stop the domain, > unbind and rebind it, then the OS on the logical domain sees the correct disk > size. Boot -r or devfsadm would not correct this. Only a unbind and re-bind > corrected it. > > I was able to grow the filesystems with out unbinding with LDom 1.0.2. The > volumes are setup as a single slice. Anyone else encounter this? > -- > This message was posted from opensolaris.org > _______________________________________________ > ldoms-discuss mailing list > ldoms-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss >
