Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Oliver Mattos <oliver.mattos08@imperial.ac.uk>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Partial Allocation
Date: Tue, 02 Dec 2008 20:18:20 -0500	[thread overview]
Message-ID: <1228267100.2048.2.camel@think.oraclecorp.com> (raw)
In-Reply-To: <1228264376.17414.4.camel@mattos-laptop>

On Wed, 2008-12-03 at 00:32 +0000, Oliver Mattos wrote:
> Hi,
> 
> I presume that in the design of BTRFS, like most other filesystems, a
> block on the underlying storage is either allocated (ie. to store
> metadata or file data), or deallocated (possibly blank or containing
> garbage left over, but the contents are irrelivant).
> 
> Does BTRFS have any system that could allow adding at a later point in
> time a feature which would allow "weak" allocation of blocks, by which I
> mean the block is allocated (ie. storing useful data), but if another
> file needs to be written which has a higher priority and there are not
> many free blocks left, then the data could be replaced.
> 

It could be done, but I would expect that any userland facility that
wanted this kind of feature would want to maintain its own cache.  Files
that disappear tend to confuse all but a very small set of applications.

For now it doesn't have broad enough applications that I'm willing to
code it up before 1.0.  But if you want to dive in, please feel free.

-chris



  reply	other threads:[~2008-12-03  1:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03  0:32 Partial Allocation Oliver Mattos
2008-12-03  1:18 ` Chris Mason [this message]
2008-12-04 12:15 ` Josef Bacik
     [not found] <1228162019.5274.36.camel@mattos-laptop>
2008-12-01 23:49 ` Partial allocation Oliver Mattos

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=1228267100.2048.2.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=oliver.mattos08@imperial.ac.uk \
    /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