From: "Hendrik Friedel" <hendrik@friedels.name>
To: "Qu Wenruo" <quwenruo.btrfs@gmx.com>,
"Chris Murphy" <lists@colorremedies.com>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re[2]: Rough (re)start with btrfs
Date: Fri, 03 May 2019 05:41:52 +0000 [thread overview]
Message-ID: <ema5c33b0a-936b-48f6-99ba-4c5a50e8a88a@ryzen> (raw)
In-Reply-To: <e6918268-1e3e-6c2d-853c-aa1eaf8e9693@gmx.com>
Hello,
-by the way: I think my mail did not appear in the list, but only
reached Chris and Qu directly. I just tried to re-send it. Could this be
caused by
1) me not a subscriber of the list
2) combined with me sending attachments
I did *not* get any error message by the server.
>> I was tempted to ask, whether this should be fixed. On the other hand, I
>> am not even sure anything bad happened (except, well, the system -at
>> least the copy- seemed to hang).
>
>Definitely needs to be fixed.
>
>With full dmesg, it's now clear that is a real dead lock.
>Something wrong with the free space cache, blocking the whole fs to be
>committed.
>
So, what's the next step? Shall I open a bug report somewhere, or is it
already on some list?
>If you still want to try btrfs, you could try "nosapce_cache" mount option.
>Free space cache of btrfs is just an optimization, you can completely
>ignore that with minor performance drop.
>
I will try that, yes.
Can you confirm, that it is unlikely, that I lost any data / damaged the
Filesystem?
Regards,
Hendrik
next prev parent reply other threads:[~2019-05-03 5:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <em9eba60a7-2c0d-4399-8712-c134f0f50d4d@ryzen>
2019-05-02 23:40 ` Rough (re)start with btrfs Qu Wenruo
2019-05-03 5:41 ` Hendrik Friedel [this message]
2019-05-03 6:05 ` Re[2]: " Chris Murphy
2019-05-04 9:31 ` Re[4]: " Hendrik Friedel
2019-05-04 19:05 ` Chris Murphy
2019-05-06 18:39 ` Re[6]: " Hendrik Friedel
2019-05-03 7:34 ` Qu Wenruo
2019-05-03 5:58 ` Chris Murphy
2019-05-03 5:52 ` Re[2]: " 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=ema5c33b0a-936b-48f6-99ba-4c5a50e8a88a@ryzen \
--to=hendrik@friedels.name \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=quwenruo.btrfs@gmx.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;
as well as URLs for NNTP newsgroup(s).