From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>,
Christian Theune <ct@flyingcircus.io>,
linux-btrfs@vger.kernel.org
Subject: Re: Downgrading kernel 4.9 to 4.4 with space_cache=v2 enabled?
Date: Fri, 24 Feb 2017 07:23:42 -0500 [thread overview]
Message-ID: <bb8ea7fc-8607-f130-47f0-94175e20e330@gmail.com> (raw)
In-Reply-To: <fe942684-deb3-08f1-d4c1-ae25a912f799@cn.fujitsu.com>
On 2017-02-23 19:54, Qu Wenruo wrote:
>
>
> At 02/23/2017 06:51 PM, Christian Theune wrote:
>> Hi,
>>
>> not sure whether it’s possible, but we tried space_cache=v2 and
>> obviously after working fine in staging it broke in production. Or
>> rather: we upgraded from 4.4 to 4.9 and enabled the space_cache. Our
>> production volume is around 50TiB usable (underlying HW Raid 6).
>>
>> The machine crashes silently every 15 hours or so and takes _ages_ to
>> reboot. It current is stuck trying to mount the local filesystems and
>> I guess btrfs is doing something, but I don’t have shell access yet.
>>
>> I’m wondering whether we can downgrade by booting back into 4.4 or
>> will this break things even further? (We’ve had some unpleasant
>> surprises with FS’ in the last months, so I thought I’d rather ask.)
>
> You could use "btrfs check --clear-space-cache" to completely cleanup
> space cache. Both v1(free space cache, file based) or v2(free space
> tree) are supported.
>
> And specially for v2 space cache (space cache tree), "btrfs check
> --clear-space-cache" will also clear the ro_compat flag, so older kernel
> should mount the fs without problem.
That's really good to know. I hadn't remembered that using mount
options didn't clear the flag.
next prev parent reply other threads:[~2017-02-24 12:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 10:51 Downgrading kernel 4.9 to 4.4 with space_cache=v2 enabled? Christian Theune
2017-02-23 12:34 ` Austin S. Hemmelgarn
[not found] ` <71958378-5AB4-4E66-8F54-60215141D1BB@flyingcircus.io>
2017-02-23 13:19 ` Christian Theune
2017-02-23 13:38 ` Austin S. Hemmelgarn
2017-02-24 18:35 ` Omar Sandoval
2017-02-24 0:54 ` Qu Wenruo
2017-02-24 12:23 ` Austin S. Hemmelgarn [this message]
2017-02-24 18:34 ` Omar Sandoval
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=bb8ea7fc-8607-f130-47f0-94175e20e330@gmail.com \
--to=ahferroin7@gmail.com \
--cc=ct@flyingcircus.io \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox