From: "Niccolò Belli" <darkbasic@linuxsystems.it>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
Cc: <linux-btrfs@vger.kernel.org>,
Clemens Eisserer <linuxhippy@gmail.com>,
Patrik Lundquist <patrik.lundquist@gmail.com>,
Chris Murphy <lists@colorremedies.com>,
Qu Wenruo <quwenruo@cn.fujitsu.com>,
Omar Sandoval <osandov@osandov.com>,
Zygo Blaxell <ce3g8jdj@umail.furryterror.org>,
<1i5t5.duncan@cox.net>
Subject: Re: btrfs ate my data in just two days, after a fresh install. ram and disk are ok. it still mounts, but I cannot repair
Date: Fri, 13 May 2016 14:10:04 +0200 [thread overview]
Message-ID: <218bfc1b-a136-45cf-b5d0-8d4c5937efbf@linuxsystems.it> (raw)
In-Reply-To: <994b4fa5-c7ef-27e1-2fc2-386ab62a16c0@gmail.com>
On venerdì 13 maggio 2016 13:35:01 CEST, Austin S. Hemmelgarn wrote:
> The fact that you're getting an OOPS involving core kernel
> threads (kswapd) is a pretty good indication that either there's
> a bug elsewhere in the kernel, or that something is wrong with
> your hardware. it's really difficult to be certain if you don't
> have a reliable test case though.
Talking about reliable test cases, I forgot to say that I definitely found
an interesting one. It doesn't lead to OOPS but perhaps something even more
interesting. While running countless stress tests I tried running some
games to stress the system in different ways. I chosed openmw (an open
source engine for Morrowind) and I played it for a while on my second
external monitor (while I watched at some monitoring tools on my first
monitor). I noticed that after playing a while I *always* lose internet
connection (I use an USB3 Gigabit Ethernet adapter). This isn't the only
thing which happens: even if the game keeps running flawlessly and the
system *seems* to work fine (I can drag windows, open the terminal...) lots
of commands simply stall (for example mounting a partition, unmounting it,
rebooting...). I can reliably reproduce it, it ALWAYS happens.
Niccolò
next prev parent reply other threads:[~2016-05-13 12:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 23:21 btrfs ate my data in just two days, after a fresh install. ram and disk are ok. it still mounts, but I cannot repair Niccolò Belli
2016-05-05 1:07 ` Chris Murphy
2016-05-05 10:36 ` Niccolò Belli
2016-05-05 17:48 ` Omar Sandoval
2016-05-06 11:38 ` Niccolò Belli
2016-05-07 15:45 ` Niccolò Belli
2016-05-07 15:58 ` Clemens Eisserer
2016-05-07 16:11 ` Niccolò Belli
2016-05-08 18:27 ` Patrik Lundquist
2016-05-09 11:52 ` Austin S. Hemmelgarn
2016-05-09 14:53 ` Niccolò Belli
2016-05-09 16:29 ` Zygo Blaxell
2016-05-09 18:21 ` Austin S. Hemmelgarn
2016-05-09 19:18 ` Duncan
2016-05-12 14:35 ` Niccolò Belli
2016-05-12 15:43 ` Austin S. Hemmelgarn
2016-05-13 11:07 ` Niccolò Belli
2016-05-13 11:35 ` Austin S. Hemmelgarn
2016-05-13 12:10 ` Niccolò Belli [this message]
2016-05-13 21:54 ` Chris Murphy
2016-05-12 16:48 ` Zygo Blaxell
2016-05-09 19:23 ` Lionel Bouton
2016-05-09 21:30 ` Chris Murphy
2016-05-07 23:35 ` Chris Murphy
2016-05-05 4:12 ` Qu Wenruo
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=218bfc1b-a136-45cf-b5d0-8d4c5937efbf@linuxsystems.it \
--to=darkbasic@linuxsystems.it \
--cc=1i5t5.duncan@cox.net \
--cc=ahferroin7@gmail.com \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linuxhippy@gmail.com \
--cc=lists@colorremedies.com \
--cc=osandov@osandov.com \
--cc=patrik.lundquist@gmail.com \
--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 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.