On Fri, Jul 26, 2013 at 10:06:20PM +0100, Richard W.M. Jones wrote: > On Fri, Jul 26, 2013 at 10:13:42PM +0200, Miloslav Trmač wrote: > > Hello all, > > with thin provisioning available, the total and free space values > > reported by a filesystem do not necessarily mean that that much space > > is _actually_ available (the actual backing storage may be smaller, or > > shared with other filesystems). > > > > If your package reports disk space usage to users, and bases this on > > filesystem free space, please consider whether it might need to take > > LVM thin provisioning into account. > > > > The same applies if your package automatically allocates a certain > > proportion of the total or available space. > > > > A quick way to check whether your package is likely to be affected, is > > to look for statfs() or statvfs() calls in C, or the equivalent in > > your higher-level library / programming language. > > Also libvirt has a whole set of APIs around storage and > free space. Yep, we need to be able to report free space on filesystems, so that apps provisioning virtual machines can get an idea of how much storage they can provide to VMs without risk of over comitting. I agree that we really want the kernel, or at least a reusable shared library, to provide some kind of interface to determine this, rather than requiring every userspace app which cares to re-invent the wheel. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
