linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roger Binns <rogerb@rogerbinns.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: What to do about df and btrfs fi df
Date: Mon, 10 Feb 2014 17:02:31 -0800	[thread overview]
Message-ID: <ldbsqr$dlg$1@ger.gmane.org> (raw)
In-Reply-To: <CAE5mzvgFLfQoaNx1eWB2z_kJW-pe1bFY_3LxDMV9XbtKApo=xw@mail.gmail.com>

-----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-----


  parent reply	other threads:[~2014-02-11  1:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 16:41 What to do about df and btrfs fi df Josef Bacik
2014-02-10 17:06 ` Hugo Mills
2014-02-10 18:24   ` cwillu
2014-02-10 18:28     ` Josef Bacik
2014-02-10 18:36       ` cwillu
2014-02-10 18:41         ` Josef Bacik
2014-02-10 18:54           ` cwillu
2014-02-10 19:05           ` Hugo Mills
2014-02-11 17:36           ` David Sterba
2014-02-17 17:08           ` David Sterba
2014-02-18  8:33             ` Goswin von Brederlow
2014-02-18 16:43               ` David Sterba
2014-02-11  1:02     ` Roger Binns [this message]
2014-02-11  3:13       ` cwillu
2014-02-11  3:35         ` ronnie sahlberg
2014-02-11 19:58         ` Roger Binns
2014-02-10 22:14   ` Goffredo Baroncelli
2014-02-10 22:26 ` Goffredo Baroncelli
2014-02-10 22:56   ` cwillu
2014-02-11 13:14   ` Josef Bacik
2014-02-11 18:20     ` Goffredo Baroncelli
2014-02-11 18:33       ` Josef Bacik
2014-02-11 18:46         ` Goffredo Baroncelli
2014-02-11 18:56       ` Hugo Mills
2014-02-12 21:03         ` Goffredo Baroncelli
2014-02-11 20:53 ` Sandy McArthur
2014-02-12  3:09   ` Kostia Khlebopros
2014-02-12 21:12     ` Goffredo Baroncelli
2014-02-12  3:55 ` Anand Jain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='ldbsqr$dlg$1@ger.gmane.org' \
    --to=rogerb@rogerbinns.com \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).