From: Chris Murphy <lists@colorremedies.com>
To: "cheater00 ." <cheater00@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem
Date: Thu, 7 Jan 2016 14:55:59 -0700 [thread overview]
Message-ID: <CAJCQCtR3Gj5K0dsAhDBo27Z6h3ki5cs6X0SrrFhC0dPPgY=4nw@mail.gmail.com> (raw)
In-Reply-To: <CA+9GZUiWQ2tAotFuq2Svkjnk+2Quz5B8UwZSSpm4SJfhqfoStQ@mail.gmail.com>
I'm not finding much about this.
http://www.spinics.net/lists/linux-btrfs/msg46537.html
http://www.spinics.net/lists/linux-btrfs/msg46279.html
The last one Anand Jain (developer) replied:
http://www.spinics.net/lists/linux-btrfs/msg46303.html
So I'm not sure if this problem is the same, and if the cause is
known. Best I can suggest is to try a newer kernel. Even 4.4.0rc8 is
stable enough to try; but there were quite a few btrfs patches for
4.3.3 as well. I would try 4.4.0 first to see if it reproduces. If
not, then try 4.3.3.
>4.3.0-040300rc7-generic #201510260712 SMP Mon Oct 26
>11:27:59 UTC 2015 i686 i686 i686 GNU/Linux
I think the other two cases are x86-64 so I don't think i686 is related.
There are quite a few messages:
swapper/6: page allocation failure: order:0, mode:0x20
[1129393.648245] CPU: 6 PID: 0 Comm: swapper/6 Tainted: G W OE
4.3.0-040300rc7-generic #201510260712
So the kernel is in a tainted state, I can't tell if that's related.
And also
usb 4-1.2: reset high-speed USB device number 7 using ehci-pci
One happens less than a minute before the first btrfs call trace. I've
had these messages also with USB drives, and they usually don't cause
a problem, and in my research it seems they can usually be ignored
except when there's subsequent problems. I ended up getting a powered
hub to put all the USB drives on and now I don't get these messages
anymore (so far anyway) and I also haven't had any Btrfs errors, which
I did rarely have happen prior to moving to the USB 3 powered hub;
even though the power shouldn't have been a factor since the drives
want 900mA at most (usually just spinning up), and standard USB 3
supplies 900mA.
Anyway, easiest is to move to a newer kernel to try to reproduce and
then start looking at hardware issues. What specific drive is
/dev/sdd? I'd make a note of that particular drive and see if it's the
same drive (not drive letter) if the problem happens again.
---
Chris Murphy
next prev parent reply other threads:[~2016-01-07 21:56 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 21:44 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem cheater00 .
2015-12-30 22:13 ` Chris Murphy
2016-01-02 2:09 ` cheater00 .
2016-01-02 2:10 ` cheater00 .
[not found] ` <CA+9GZUiWQ2tAotFuq2Svkjnk+2Quz5B8UwZSSpm4SJfhqfoStQ@mail.gmail.com>
2016-01-07 21:55 ` Chris Murphy [this message]
[not found] ` <CA+9GZUjLcRnRX_mwO-McXWFd+G4o3jtBENMLnszg-rJTn6vL1w@mail.gmail.com>
[not found] ` <CAJCQCtRhYZi9nqWP_LYmZeg1yRQVkpnmUDQ-P5o1-gc-3w+Pdg@mail.gmail.com>
2016-01-09 20:00 ` cheater00 .
2016-01-09 20:26 ` Hugo Mills
2016-01-09 20:59 ` cheater00 .
2016-01-09 21:04 ` Hugo Mills
2016-01-09 21:07 ` cheater00 .
2016-01-09 21:15 ` Hugo Mills
2016-01-10 3:59 ` cheater00 .
2016-01-10 6:16 ` Russell Coker
2016-01-10 22:24 ` cheater00 .
2016-01-10 22:32 ` Lionel Bouton
2016-01-11 13:05 ` Austin S. Hemmelgarn
2016-01-11 13:11 ` cheater00 .
2016-01-11 13:30 ` cheater00 .
2016-01-11 13:45 ` cheater00 .
2016-01-11 14:04 ` cheater00 .
2016-01-12 2:18 ` Duncan
2016-08-04 16:53 ` Lutz Vieweg
2016-08-04 20:30 ` Chris Murphy
2016-08-05 10:56 ` Lutz Vieweg
2016-08-05 12:12 ` Austin S. Hemmelgarn
2016-08-05 13:14 ` Lutz Vieweg
2016-08-05 20:03 ` Gabriel C
2016-08-25 15:48 ` Lutz Vieweg
2016-01-11 14:10 ` Austin S. Hemmelgarn
2016-01-11 16:02 ` cheater00 .
2016-01-11 16:33 ` cheater00 .
2016-01-11 20:29 ` Henk Slager
2016-01-12 1:16 ` Duncan
2016-01-11 0:13 ` Chris Murphy
2016-01-11 9:03 ` Hugo Mills
2016-01-11 13:04 ` cheater00 .
2016-01-11 21:31 ` Chris Murphy
2016-01-11 22:10 ` Hugo Mills
2016-01-11 22:20 ` Chris Murphy
2016-01-11 22:30 ` Hugo Mills
2016-01-11 22:39 ` Chris Murphy
2016-01-11 23:07 ` Hugo Mills
2016-01-11 23:12 ` cheater00 .
2016-01-11 23:05 ` cheater00 .
2016-01-12 2:05 ` Duncan
2016-01-11 22:57 ` cheater00 .
2016-01-10 14:14 ` Henk Slager
2016-01-10 23:47 ` cheater00 .
2016-01-11 0:24 ` Chris Murphy
2016-01-11 6:07 ` cheater00 .
2016-01-11 6:24 ` cheater00 .
2016-01-11 7:54 ` cheater00 .
2016-01-12 0:35 ` Duncan
2016-01-11 19:50 ` Henk Slager
2016-01-11 23:03 ` cheater00 .
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='CAJCQCtR3Gj5K0dsAhDBo27Z6h3ki5cs6X0SrrFhC0dPPgY=4nw@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=cheater00@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).