From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: A note on spotting "bugs" [Was: ENOSPC after conversion]
Date: Sat, 13 Dec 2014 01:12:15 +0000 (UTC) [thread overview]
Message-ID: <pan$93dc7$f46dda26$f7d33e3f$b328e05d@cox.net> (raw)
In-Reply-To: 548AEDD6.1090904@pobox.com
Robert White posted on Fri, 12 Dec 2014 05:29:58 -0800 as excerpted:
> This still doesnt say _anything_ is wrong with your filesystem except
> that it doesn't have enough _raw_ space to create a 2-ish gig extent.
What's wrong with the filesystem is that there shouldn't /be/ a need to
create a 2-ish gig extent. All btrfs native structures are 1 GiB each or
smaller, and the completed-without-error btrfs fi defrag should have
eliminated any > 1 GiB structures remaining from the conversion from
ext*, such that btrfs balance only has to deal with <= 1 GiB structures.
So that balance is having to deal with a 2-ish gig extent at all is
indicative of a bug. Balance isn't prepared to have to allocate 2-ish
GiB extents in the first place as that's beyond it's design specs.
--
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-12-13 1:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 8:18 ENOSPC after conversion [Was: Fixing Btrfs Filesystem Full Problems typo?] Patrik Lundquist
2014-12-11 10:18 ` Robert White
2014-12-11 23:01 ` Patrik Lundquist
2014-12-12 0:36 ` Robert White
2014-12-12 1:10 ` Robert White
2014-12-11 22:00 ` A note on spotting "bugs" [Was: ENOSPC after conversion] Robert White
2014-12-12 6:42 ` Patrik Lundquist
2014-12-12 13:29 ` Robert White
2014-12-12 14:09 ` Patrik Lundquist
2014-12-13 1:12 ` Duncan [this message]
2014-12-13 3:10 ` Robert White
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$93dc7$f46dda26$f7d33e3f$b328e05d@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.