From: Christoph Hellwig <hch@infradead.org>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs space used issue
Date: Mon, 5 Mar 2018 07:28:27 -0800 [thread overview]
Message-ID: <20180305152827.GA27477@infradead.org> (raw)
In-Reply-To: <pan$bee0f$57d3b021$cd11cf8a$d3c1d93d@cox.net>
On Sat, Mar 03, 2018 at 06:59:26AM +0000, Duncan wrote:
> Indeed. Preallocation with COW doesn't make the sense it does on an
> overwrite-in-place filesystem.
It makes a whole lot of sense, it just is a little harder to implement.
There is no reason not to preallocate specific space, or if you aren't
forced to be fully log structured by the medium, specific blocks to
COW into. It just isn't quite as trivial as for a rewrite in place
file system to implement.
next prev parent reply other threads:[~2018-03-05 15:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 13:09 btrfs space used issue vinayak hegde
2018-02-27 13:54 ` Austin S. Hemmelgarn
2018-02-28 6:01 ` vinayak hegde
2018-02-28 15:22 ` Andrei Borzenkov
2018-03-01 9:26 ` vinayak hegde
2018-03-01 10:18 ` Andrei Borzenkov
2018-03-01 12:25 ` Austin S. Hemmelgarn
2018-03-03 6:59 ` Duncan
2018-03-05 15:28 ` Christoph Hellwig [this message]
2018-03-05 16:17 ` Austin S. Hemmelgarn
2018-02-28 19:09 ` Duncan
2018-02-28 19:24 ` Austin S. Hemmelgarn
2018-02-28 19:54 ` Duncan
2018-02-28 20:15 ` Austin S. Hemmelgarn
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=20180305152827.GA27477@infradead.org \
--to=hch@infradead.org \
--cc=1i5t5.duncan@cox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.