From: Hugo Mills <hugo@carfax.org.uk>
To: Hendrik Friedel <hendrik@friedels.name>
Cc: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: free space inode generation (0) did not match free space cache generation
Date: Tue, 25 Mar 2014 20:10:20 +0000 [thread overview]
Message-ID: <20140325201020.GC7442@carfax.org.uk> (raw)
In-Reply-To: <5331E10E.6080806@friedels.name>
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
On Tue, Mar 25, 2014 at 09:03:26PM +0100, Hendrik Friedel wrote:
> Hi,
>
> >Well, given the relative immaturity of btrfs as a filesystem at this
> >point in its lifetime, I think it's acceptable/tolerable. However, for a
> >filesystem feted[1] to ultimately replace the ext* series as an assumed
> >Linux default, I'd definitely argue that the current situation should be
> >changed such that btrfs can automatically manage its own de-allocation at
> >some point, yes, and that said "some point" really needs to come before
> >that point at which btrfs can be considered an appropriate replacement
> >for ext2/3/4 as the assumed default Linux filesystem of the day.
>
> Agreed! I hope, this is on the ToDo List?!
https://btrfs.wiki.kernel.org/index.php/Project_ideas#Block_group_reclaim
Yes. :)
> >[1] feted: celebrated, honored. I had to look it up to be sure my
> >intuition on usage was correct, and indeed I had spelled it wrong
>
> :-)
Did you mean "fated": intended, destined?
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- IMPROVE YOUR ORGANISMS!! -- Subject line of spam email ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2014-03-25 20:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <532DF38B.40409@friedels.name>
2014-03-22 21:16 ` free space inode generation (0) did not match free space cache generation Hendrik Friedel
2014-03-22 23:32 ` Duncan
2014-03-24 20:52 ` Hendrik Friedel
2014-03-25 13:00 ` Duncan
2014-03-25 20:03 ` Hendrik Friedel
2014-03-25 20:10 ` Hugo Mills [this message]
2014-03-25 21:28 ` Duncan
2014-03-25 21:50 ` Hugo Mills
2014-03-28 7:32 ` Hendrik Friedel
2014-03-22 18:13 Hendrik Friedel
2014-03-22 19:23 ` Duncan
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=20140325201020.GC7442@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=1i5t5.duncan@cox.net \
--cc=hendrik@friedels.name \
--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