From: Florian Hofmann <fhofmann@techfak.uni-bielefeld.de>
To: Leonidas Spyropoulos <artafinde@gmail.com>
Cc: Josef Bacik <jbacik@fusionio.com>, cwillu <cwillu@cwillu.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Fwd: Current State of BTRFS
Date: Mon, 11 Feb 2013 22:19:41 +0100 [thread overview]
Message-ID: <CAM-0MpVb_8ZXXsfi=-3u_HaZ3xiDTod_BXSU6u_o2vHun+fBjw@mail.gmail.com> (raw)
In-Reply-To: <CAAeznToauNWzvwxR5giHhEpDo_ADNywEBw_wSQD4gViad3rb4g@mail.gmail.com>
@Leonidas: I don't think so ... this is running on a i7 core and lzo
is pretty damn fast.
2013/2/11 Leonidas Spyropoulos <artafinde@gmail.com>:
> On Mon, Feb 11, 2013 at 4:05 PM, Josef Bacik <jbacik@fusionio.com> wrote:
>> On Fri, Feb 08, 2013 at 04:12:17PM -0700, Florian Hofmann wrote:
>>> I ran it as root. The first times there was no output whatsoever. This
>>> time triggering gave the SysRq : Show Blocked State line. Strange
>>>
>>
>> Well that's weird, it looks like you don't have any blocked tasks, so either
>> sysrq+w is screwing up or you are getting stuck in something CPU intensive. Try
>> doing sysrq+w next time it happens again and also run top and see if something
>> is using up 100% of the CPU. If it's something chewing up CPU then I'll tell
>> you how to figure out what's going on. Thanks,
>>
> I noticed you have the FS mounted with compress flag (compress=lzo).
> Could it be that your CPU is bottle-necking the process?
>
>> Josef
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
> --
> Caution: breathing may be hazardous to your health.
>
> #include <stdio.h>
> int main(){printf("%s","\x4c\x65\x6f\x6e\x69\x64\x61\x73");}
next prev parent reply other threads:[~2013-02-11 21:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAM-0MpVDJ+TGC6x9JHd+wG5dsACdN4Y+JFgksQCsiwzGQYNanA@mail.gmail.com>
2013-02-08 21:30 ` Fwd: Current State of BTRFS Florian Hofmann
2013-02-08 21:37 ` Josef Bacik
2013-02-08 22:53 ` Florian Hofmann
2013-02-08 22:56 ` Florian Hofmann
2013-02-08 23:09 ` cwillu
2013-02-08 23:12 ` Florian Hofmann
2013-02-11 16:05 ` Josef Bacik
2013-02-11 16:14 ` Leonidas Spyropoulos
2013-02-11 21:19 ` Florian Hofmann [this message]
2013-02-08 23:10 ` Florian Hofmann
2013-02-09 10:30 ` Marc MERLIN
2013-02-09 13:35 ` Florian Hofmann
2013-02-11 23:04 ` Chris Samuel
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='CAM-0MpVb_8ZXXsfi=-3u_HaZ3xiDTod_BXSU6u_o2vHun+fBjw@mail.gmail.com' \
--to=fhofmann@techfak.uni-bielefeld.de \
--cc=artafinde@gmail.com \
--cc=cwillu@cwillu.com \
--cc=jbacik@fusionio.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).