ick! yes Ghe, agree but I would not advice this process, even though I have done this many time and works a huge % of the time, it’s not a save solution. parted then will be better if he really needs to address this resize and yes to keep in mind that XFS does not resize down at all. So the best solution as it has been already advised is to spin up a new one and move the data there.
Remo > On Feb 10, 2016, at 06:51, Ghe Rivero <ghe.riv...@gmail.com> wrote: > > There could be situations where resizing (up or down) an instance could be an > option (like critical non-ha services although this is a real bad policy) but > the proper way to operate a cloud is to spin up and kill as many instances as > needed. But if you really need to shrink an instance, it's just not a problem > of cloud capabilities. The filesystem of your instance must support it (a no > go if it's XFS and in case you use ext4, it can be done in offline mode). > > Ghe Rivero > > Quoting Mārtiņš Jakubovičs (2016-02-09 12:00:51) >> Hello, >> >> I can't find documentation about this. >> Is it possible to resize instance down when use CEPH as storage? >> Right now I try to resize down and I receive error: >> >> Flavor's disk is too small for requested image. Flavor disk is 42949672960 >> bytes, image is 21474836480 bytes. >> >> OS Liberty, >> Ubuntu 14.04 x64, >> CEPH 0.94.5 > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > !DSPAM:1,56bb53ce33081451394549! > _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
