From: Roman Mamedov <rm@romanrm.net>
To: Noah Massey <noah.massey@gmail.com>
Cc: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
Thomas <c.monty@web.de>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Issue: errno:28 (No space left on device)
Date: Tue, 9 Aug 2016 18:56:05 +0500 [thread overview]
Message-ID: <20160809185605.3fc06903@natsu> (raw)
In-Reply-To: <CADfjVrgzMNrsfv=S9+zPBZEcvkfiP=fg-Pi8gB+W1gYaJTxcRA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
On Tue, 9 Aug 2016 09:39:45 -0400
Noah Massey <noah.massey@gmail.com> wrote:
> Since your data and metadata profiles are both 'single', you may want
> to consider creating the filesystem with the --mixed option, which
> allows / forces BTRFS to use a single collection of data blocks for
> both data and metadata.
That also seems to be detrimental to performance, I had servers with mixed
profile FSes which went painfully slow after a couple of years (daily snapshot
creation and deletion, ~30-60 snapshots kept at all times), migrated them all
now to the regular split profile. Fresh off mkfs they are fast of course, so
not entirely certain "mixed" was the culprit, will see.
One more problem with mixed is that you can't use the leaf and nodesize of 16k,
which are accepted to be faster than the older default (and mixed's only
option) of 4k.
--
With respect,
Roman
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-08-09 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 11:50 Issue: errno:28 (No space left on device) Thomas
2016-08-09 12:21 ` Tomasz Torcz
2016-08-09 12:56 ` Austin S. Hemmelgarn
2016-08-09 13:39 ` Noah Massey
2016-08-09 13:56 ` Roman Mamedov [this message]
2016-08-09 13:47 ` Josef Bacik
-- strict thread matches above, loose matches on Subject: below --
2016-08-09 9:09 Thomas
2016-08-09 9:06 Thomas
2016-08-09 16:50 ` Chris Murphy
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=20160809185605.3fc06903@natsu \
--to=rm@romanrm.net \
--cc=ahferroin7@gmail.com \
--cc=c.monty@web.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=noah.massey@gmail.com \
/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.