From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Cc: 4brad@templetons.com
Subject: Re: btrfs-transacti hangs system for several seconds every few minutes
Date: Mon, 30 Mar 2020 11:29:19 +0900 [thread overview]
Message-ID: <94d08f2b57dd2df746436a0d6bb5f51e@wpkg.org> (raw)
> I wonder why they put 5.3.0 as the standard advanced Kernel in Ubuntu
> LTS if it has a data corruption bug. I don't know if I've seen any
> release of 5.4.14 in a PPA yet -- manual kernel install is such a pain
> the few times I have done it.
You have all kernels compiled as packages here (for Ubuntu):
https://kernel.ubuntu.com/~kernel-ppa/mainline/
So just download two deb packages, dpkg -i, and done.
btrfs can be still not quite as stable as one would wish, but the
following work well for me on quite many servers:
- use a recent kernel - late 5.5.x, now perhaps 5.6 - will typically
work better for btrfs than a default distribution kernel
- use "noatime" mount option
- use "space_cache=v2" mount option
- absolutely do not use qgroups (make sure this command returns an error
saying that quotas are not enabled): btrfs qgroup show /mount/point
- if using RAID-5, make sure to use RAID-1 for metadata (and raid1c3
metadata for RAID-6 data)
- if you use any software automation, make sure that it doesn't
accidentally re-enable quotas (in btrfs, there is no mount flag for
quotas, unlike in other filesystems, so it's not intuitive to say if the
quotas are enabled or not)
Tomasz Chmielewski
https://lxadm.com
next reply other threads:[~2020-03-30 2:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 2:29 Tomasz Chmielewski [this message]
2020-03-30 5:56 ` btrfs-transacti hangs system for several seconds every few minutes Andrei Borzenkov
2020-03-30 8:11 ` Brad Templeton
2020-03-30 8:35 ` Tomasz Chmielewski
2020-03-31 4:20 ` Zygo Blaxell
-- strict thread matches above, loose matches on Subject: below --
2020-03-29 4:03 Brad Templeton
2020-03-29 13:14 ` Qu Wenruo
2020-03-29 17:58 ` Brad Templeton
2020-03-29 18:09 ` Zygo Blaxell
2020-03-28 18:26 Brad Templeton
2020-03-28 21:20 ` Zygo Blaxell
[not found] ` <7778ece0-67d4-8d1c-b773-35f07d81dcbe@templetons.com>
2020-03-29 6:42 ` Zygo Blaxell
2020-03-30 22:14 ` Chris Murphy
2020-03-31 4:04 ` Zygo Blaxell
2020-03-29 0:58 ` Qu Wenruo
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=94d08f2b57dd2df746436a0d6bb5f51e@wpkg.org \
--to=mangoo@wpkg.org \
--cc=4brad@templetons.com \
--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