From: Leonidas Spyropoulos <artafinde@gmail.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Ccache on btrfs
Date: Fri, 17 Oct 2014 20:24:38 +0100 [thread overview]
Message-ID: <20141017192438.GA20983@sune> (raw)
In-Reply-To: <CAGqmi7751HOLJ5xU+NfoZSjTQhgYME-9b36hgJt0oG6w+Ft-CA@mail.gmail.com>
On 17/10/14, Timofey Titovets wrote:
> i use ccache and often compile linux from git,
> I don't catch any errors with it.
>
Interesting, I re-enabled ccache on an ext4 partition (HDD) and worked
fine. So I suspect it's something to do with btrfs and SSD. My mount
options are:
/dev/sda3 on /home type btrfs (rw,relatime,ssd,discard,nospace_cache)
The problem is that I can't get hold of kernel panic since it's not in
the journal [1]. I don't know a way to get hold of the kernel panic log
to help anyway.
What would it be useful to debug it?
[1] using systemd
Leonidas
next prev parent reply other threads:[~2014-10-17 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 17:11 Ccache on btrfs Leonidas Spyropoulos
[not found] ` <CAGqmi7751HOLJ5xU+NfoZSjTQhgYME-9b36hgJt0oG6w+Ft-CA@mail.gmail.com>
2014-10-17 19:24 ` Leonidas Spyropoulos [this message]
2014-10-17 20:32 ` Josef Bacik
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=20141017192438.GA20983@sune \
--to=artafinde@gmail.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;
as well as URLs for NNTP newsgroup(s).