From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Fixing Btrfs Filesystem Full Problems typo?
Date: Mon, 24 Nov 2014 04:40:44 +0000 (UTC) [thread overview]
Message-ID: <pan$82068$d0cc4786$993a408a$1e0e7a67@cox.net> (raw)
In-Reply-To: pan.2014.11.23.22.49.01@googlemail.com
Holger Hoffstätte posted on Sun, 23 Nov 2014 22:49:01 +0000 as excerpted:
> On Sun, 23 Nov 2014 13:16:50 -0800, Marc MERLIN wrote:
>
> (snip)
>
>> That makes sense. I'll try to synthetize all this and rewrite my blog
>> post and the wiki to make this clearer.
>
> Maybe also add that as of 3.18 empty block groups are automatically
> collected, so balancing to prevent ENOSPC-by-empty-chunks is no longer
> necessary. This works pretty well; I haven't run balance in weeks, and
> my total-vs.-used overhead has always been <10 GB.
For those of us who have been around btrfs for awhile, this still sounds
like the stuff if science fiction, perhaps possible sometime in the
future, but definitely not something we're yet used to having actually
automatically handled for us.
=:^)
So I think we're all glad it's here now, but kind of holding our breath
waiting for that bug due to this that stops everything cold. I think the
feeling is, OK, but let's not rock the boat too much in our haste to
celebrate, or we might find ourselves unexpectedly in the water once
again. Let's just go on teaching people to swim, assuming they'll need
to know how, and if they never do, well then that's a bonus! =:^)
But I think once we get into the 3.19 development cycle, if there's no
critical bugs with this 3.18 feature yet, then and only then are we
likely to start really talking about it. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-11-24 4:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA7pwKNH-Cbd+_D+sCEJxxdervLC=_3_AzaywSE3mXi8MLydxw@mail.gmail.com>
2014-11-22 22:26 ` Fixing Btrfs Filesystem Full Problems typo? Marc MERLIN
2014-11-22 23:26 ` Patrik Lundquist
2014-11-22 23:46 ` Marc MERLIN
2014-11-23 0:05 ` Hugo Mills
2014-11-23 1:07 ` Marc MERLIN
2014-11-23 7:52 ` Duncan
2014-11-23 15:12 ` Patrik Lundquist
2014-11-24 4:23 ` Duncan
2014-11-24 12:35 ` Patrik Lundquist
2014-12-09 22:29 ` Patrik Lundquist
2014-12-09 23:13 ` Robert White
2014-12-10 7:19 ` Patrik Lundquist
2014-12-10 12:17 ` Robert White
2014-12-10 13:11 ` Duncan
2014-12-10 18:56 ` Patrik Lundquist
2014-12-10 22:28 ` Robert White
2014-12-11 4:13 ` Duncan
2014-12-11 10:29 ` Patrik Lundquist
2014-12-11 6:16 ` Patrik Lundquist
2014-12-10 13:36 ` Patrik Lundquist
2014-12-11 8:42 ` Robert White
2014-12-11 9:02 ` Duncan
2014-12-11 9:55 ` Patrik Lundquist
2014-12-11 11:01 ` Robert White
2014-12-09 23:20 ` Robert White
2014-12-09 23:48 ` Robert White
2014-12-10 0:01 ` Robert White
2014-12-10 12:47 ` Duncan
2014-12-10 20:11 ` Patrik Lundquist
2014-12-11 4:02 ` Duncan
2014-12-11 4:49 ` Duncan
2014-11-23 21:16 ` Marc MERLIN
2014-11-23 22:49 ` Holger Hoffstätte
2014-11-24 4:40 ` Duncan [this message]
2014-12-07 21:38 ` Marc MERLIN
2014-11-24 18:05 ` Brendan Hide
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='pan$82068$d0cc4786$993a408a$1e0e7a67@cox.net' \
--to=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.