From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: "swami@petaramesh.org" <swami@petaramesh.org>,
linux-btrfs@vger.kernel.org
Cc: Christoph Anton Mitterer <calestyo@scientia.net>
Subject: Re: Re : Massive filesystem corruption since kernel 5.2 (ARCH)
Date: Tue, 27 Aug 2019 20:34:41 +0800 [thread overview]
Message-ID: <4aec59db-c4df-276e-28ca-586e8df89ad2@gmx.com> (raw)
In-Reply-To: <-z770dp-y45icx-naspi1dhhf7m-b1jjq3853x22lswnef-p5g363n8kd2f-vdijlg-jk4z4q-raec5-em5djr-et1h33i4xib8jxzw1zxyza74-miq3zn-e4azxaaeyo3abtrf6zj8nb18-hbhrrmnr1ww1.1566894946135@email.android.com>
On 2019/8/27 下午4:35, swami@petaramesh.org wrote:
> Hi Qu,
>
> Sorry for top-posting (my phone, uh...)
>
> I meant that I had understood that the V2 space cache was preferable to
> V1 only for multi-TB filesystems.
>
> So would you advise to use V2 space cache also for filesystems < 1 TB ?
Sorry, I'm not that familiar with space cache/tree code to do any
recommendation based on code.
My recommendation is, disable space cache if in doubt. Simple and
straightforward.
Thanks,
Qu
>
> TIA.
>
> Kind regards.
>
>
>
> -------- Message original --------
> Objet : Re: Massive filesystem corruption since kernel 5.2 (ARCH)
> De : Qu Wenruo
> À : Swâmi Petaramesh ,linux-btrfs@vger.kernel.org
> Cc : Christoph Anton Mitterer
>
>
> > or to use the V2 space
> > cache generally speaking, on any machine that I use (I had
> understood it
> > was useful only on multi-TB filesystems...)
>
> 10GiB is enough to create large enough block groups to utilize free
> space cache.
> So you can't really escape from free space cache.
>
next prev parent reply other threads:[~2019-08-27 12:34 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-24 17:44 Massive filesystem corruption since kernel 5.2 (ARCH) Christoph Anton Mitterer
2019-08-25 10:00 ` Swâmi Petaramesh
2019-08-27 0:00 ` Christoph Anton Mitterer
2019-08-27 5:06 ` Swâmi Petaramesh
2019-08-27 6:13 ` Swâmi Petaramesh
2019-08-27 6:21 ` Qu Wenruo
2019-08-27 6:34 ` Swâmi Petaramesh
2019-08-27 6:52 ` Qu Wenruo
2019-08-27 9:14 ` Swâmi Petaramesh
2019-08-27 12:40 ` Hans van Kranenburg
2019-08-29 12:46 ` Oliver Freyermuth
2019-08-29 13:08 ` Christoph Anton Mitterer
2019-08-29 13:09 ` Swâmi Petaramesh
2019-08-29 13:11 ` Qu Wenruo
2019-08-29 13:17 ` Oliver Freyermuth
2019-08-29 17:40 ` Oliver Freyermuth
[not found] ` <-z770dp-y45icx-naspi1dhhf7m-b1jjq3853x22lswnef-p5g363n8kd2f-vdijlg-jk4z4q-raec5-em5djr-et1h33i4xib8jxzw1zxyza74-miq3zn-e4azxaaeyo3abtrf6zj8nb18-hbhrrmnr1ww1.1566894946135@email.android.com>
2019-08-27 12:34 ` Qu Wenruo [this message]
2019-08-27 10:59 ` Swâmi Petaramesh
2019-08-27 11:11 ` Alberto Bursi
2019-08-27 11:20 ` Swâmi Petaramesh
2019-08-27 11:29 ` Alberto Bursi
2019-08-27 11:45 ` Swâmi Petaramesh
2019-08-27 17:49 ` Swâmi Petaramesh
2019-08-27 22:10 ` Chris Murphy
2019-08-27 12:52 ` Michal Soltys
2019-09-12 7:50 ` Filipe Manana
2019-09-12 8:24 ` James Harvey
2019-09-12 9:06 ` Filipe Manana
2019-09-12 9:09 ` Holger Hoffstätte
2019-09-12 10:53 ` Swâmi Petaramesh
2019-09-12 12:58 ` Christoph Anton Mitterer
2019-10-14 4:00 ` Nicholas D Steeves
2019-09-12 8:48 ` Swâmi Petaramesh
2019-09-12 13:09 ` Christoph Anton Mitterer
2019-09-12 14:28 ` Filipe Manana
2019-09-12 14:39 ` Christoph Anton Mitterer
2019-09-12 14:57 ` Swâmi Petaramesh
2019-09-12 16:21 ` Zdenek Kaspar
2019-09-12 18:52 ` Swâmi Petaramesh
2019-09-13 18:50 ` Pete
[not found] ` <CACzgC9gvhGwyQAKm5J1smZZjim-ecEix62ZQCY-wwJYVzMmJ3Q@mail.gmail.com>
2019-10-14 2:07 ` Adam Bahe
2019-10-14 2:19 ` Qu Wenruo
2019-10-14 17:54 ` 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=4aec59db-c4df-276e-28ca-586e8df89ad2@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=swami@petaramesh.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;
as well as URLs for NNTP newsgroup(s).