On Thu, Mar 10, 2011 at 08:36:29AM +1100, Dave Chinner wrote: > I can see how this would be advantageous from a management > perspective for growing LVM pools, but I can see quite a few > problems with extending that to automatically growing filesystems > above LVM. e.g. The LUN resizes, the PV is expanded, the VG is > expanded, but which LV in the VG is going to make use the new space? You'd handle that by configuration settings under sysadmin control. There are plenty of situations where there would be an 'obvious' LV to extend. > Similarly, you can't safely shrink a filesystem from the bottom up - > the filesystem has to empty the space first before it is safe to > shrink it. How would you handle this from a bottom-up driven > change? Obviously there are limits, and passing a message "Prepare to be made smaller by X" up the stack probably isn't very feasible. Alasdair -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
