On Mon, 9 Aug 2010, Yehuda Sadeh Weinraub wrote: > On Mon, Aug 9, 2010 at 3:38 AM, Wido den Hollander <wido@xxxxxxxxx> wrote: > > Hi Xiaoguang, > > > > I don't have a RBD system running at the moment, so i can't check my > > commands. > > > > But when you have /dev/rbd0, you can remove this device with: > > > > echo 0 > /sys/class/rbd/remove > > > > There might be a resize option, see: > > http://tracker.newdream.net/issues/42 > > > > echo 0 > /sys/class/rbd/refresh > > > > This will update the list of snapshots, but will not resize a mapped > device. For doing that you'll need to remove/add the device. > Also, it is highly unrecommended to alter the image while it is > mapped, as there is no proper locking and notification mechanism. Some file systems (ext3 and btrfs for sure, probably xfs?) can handle online expansion when the underlying block device grows. Is there anything preventing us from making the rbd refresh allow bdev expansion at least? I wonder if something like LVM lets you shrink a mounted bdev? sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
