It's more or less a Ceph bug; the patch fixing this is in the 3.9-rc's (although it should backport trivially if you're willing to build a kernel: 92a49fb0f79f3300e6e50ddf56238e70678e4202). You can look at http://tracker.ceph.com/issues/3793 if you want details. -Greg Software Engineer #42 @ http://inktank.com | http://ceph.com On Tue, Apr 9, 2013 at 6:51 PM, dawn li <defence986@xxxxxxxxx> wrote: > Hello everyone, > I have used the latest version 0.60 ceph in the ceph-server and the > latest linux kernel 3.8.6 in the ceph-client. > Howerver, the problem still exists in my ceph client. As follows. > I have mounted the ceph path to my ceph client with the command "mount > -t ceph * *". > The allocation size is normal when viewed through the command "df -h", > however, > the allocation size become very large and the capacity size become too > small > when viewed through the command "pool-info" in the tool "virsh". > Is it the bug of the ceph? Any help would be grateful. Thanks for your > help. > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > -- 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
