From: Chris Mason <clm@fb.com>
To: Morten Stevens <mstevens@fedoraproject.org>,
<linux-btrfs@vger.kernel.org>
Subject: Re: btrfs 3.16.2 system crash
Date: Mon, 8 Sep 2014 19:14:32 -0400 [thread overview]
Message-ID: <540E3858.8060904@fb.com> (raw)
In-Reply-To: <CAKSJeFLRK5PaZMd=KkkLNe_G_h86CYYNTrKVyt5eWzdKU+NbAw@mail.gmail.com>
On 09/08/2014 06:51 PM, Morten Stevens wrote:
> Hi,
>
> After some testing with the latest stable 3.16.2 kernel on my Fedora
> 20 test-vm and a small filesystem
> test with btrfs causes the system to crash.
>
> Kernel: 3.16.2
> Mount options: rw,seclabel,relatime,compress=lzo,space_cache
>
> The test is really simple: only writing 16 GB files on the disk with dd
> # dd if=/dev/zero of=ddfile bs=8k count=2000000
>
> You need to run it multiple times, after some time the host gets into
> a non-responsive
> state.
Hi Morten,
I haven't seen that one, and I ran an overnight stress before sending
out the stable patches. But, let me try here.
-chris
next parent reply other threads:[~2014-09-08 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKSJeFLRK5PaZMd=KkkLNe_G_h86CYYNTrKVyt5eWzdKU+NbAw@mail.gmail.com>
2014-09-08 23:14 ` Chris Mason [this message]
2014-09-10 0:42 ` btrfs 3.16.2 system crash Chris Mason
2014-09-10 11:24 Morten Stevens
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=540E3858.8060904@fb.com \
--to=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mstevens@fedoraproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.