From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: linux-btrfs.tebulin@xoxy.net, linux-btrfs@vger.kernel.org
Subject: Re: Kernel 3.19 and still "disk full" even though 'btrfs fi df" reports enough room left?
Date: Thu, 19 Nov 2015 07:28:34 -0500 [thread overview]
Message-ID: <564DC072.4060508@gmail.com> (raw)
In-Reply-To: <564CC90F.3060703@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
On 2015-11-18 13:53, linux-btrfs.tebulin@xoxy.net wrote:
>
> P.S.: Just as user feedback: For /srv I'm using on the very same system
> ZFS since the very first day. With snapshots & all the fancy stuff like
> ZRAID-1, lz4, ... My number of Issues there: 0
Since other people have adequately answered the main questions, I'll
just comment on this.
In general, ZFS is not a good comparison to BTRFS for anything but
features. Just the open source version of ZFS has been around for more
than a decade, and it existed as proprietary code for quite a while
before that. As such, it's had a lot longer to stabilize, has had
exponentially more testing, and in general is a lot more reliable. As
such, aside from feature comparisons, ZFS is going to win in almost all
tests of performance, reliability, and usability for the foreseeable
future. This doesn't mean you shouldn't use BTRFS (ZFS got to where it
is now exactly because _a lot_ of people use it), it just means you need
to do a lot of homework, and ideally keep you system actually up to date
(having all updates installed on Ubuntu doesn't really count in this
case, they're pretty bad sometimes about not properly tracking upstream
development (although they are significantly better than regular Debian)).
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-11-19 12:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 18:53 Kernel 3.19 and still "disk full" even though 'btrfs fi df" reports enough room left? linux-btrfs.tebulin
2015-11-18 19:08 ` Hugo Mills
2015-11-19 0:42 ` Qu Wenruo
2015-11-19 2:16 ` Duncan
2015-11-20 11:39 ` Dmitry Katsubo
2015-11-20 13:21 ` Austin S Hemmelgarn
2015-11-20 13:27 ` Hugo Mills
2015-11-20 13:52 ` Austin S Hemmelgarn
2015-11-20 16:39 ` Dmitry Katsubo
2015-11-19 17:35 ` linux-btrfs.tebulin
2015-11-19 18:28 ` Hugo Mills
2015-11-19 18:45 ` linux-btrfs.tebulin
2015-11-19 18:56 ` linux-btrfs.tebulin
2015-11-19 19:26 ` linux-btrfs.tebulin
2015-11-20 3:14 ` Duncan
2015-11-20 9:38 ` linux-btrfs.tebulin
2015-11-20 10:44 ` Duncan
2015-11-20 14:25 ` Dmitry Katsubo
2015-11-19 20:18 ` Austin S Hemmelgarn
2015-11-19 5:58 ` Roman Mamedov
2015-11-19 8:31 ` Patrik Lundquist
2015-11-19 12:28 ` Austin S Hemmelgarn [this message]
2015-11-20 2:11 ` Duncan
2015-11-20 13:13 ` 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=564DC072.4060508@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs.tebulin@xoxy.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.