-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/02/14 10:24, cwillu wrote: > The regular df data used number should be the amount of space required > to hold a backup of that content (assuming that the backup maintains > reflinks and compression and so forth). > > There's no good answer for available space; I think the flipside of the above works well. How large a group of files can you expect to create before you will get ENOSPC? That for example is the check code does that looks at df - "I need to put in XGB of files - will it fit?" It is also what users do. This is also what NTFS under Windows does with compression. If it says you have 5GB of space left then you will be able to put in 5GB of uncompressible files. Of course if they are compressible then you don't end up consuming all the free space. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) iEYEARECAAYFAlL5dqcACgkQmOOfHg372QQBzgCgyrvj+WnZevjEDdgbAFd2nHaD H98AoK0ZSDwZJpSMIdXpGYZGjWuPpGTh =xJ+X -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
