From: Sean Clarke <sean.clarke@sec-consulting.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: 3.11 and 3.12rc continual hard lock ups
Date: Wed, 23 Oct 2013 20:26:15 +0100 [thread overview]
Message-ID: <CAHCKNJj2=qfWEpWWUOBit5cJakwd+oFr1U-xj8MS-w9oQo6YQg@mail.gmail.com> (raw)
Hi,
I have an Intel Core i7 based fileserver with 18TB BTRFS in a 6x
3TB RAID 1+0 configuration. The system was working fine running Ubuntu
13.04 (kernel 3.11.0-12-generic). The system was upgraded to Ubuntu
13.10 (kernel 3.11) and began to lock up daily, sometimes every couple
of hours. Previously it never crashed and was only taken down for
maintenance so a bug was files on launchpad
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237794).
I have updated the system with mainline kernels "3.12.0-999-generic
#201310090426" and "3.12.0-999-generic #201310170405" and still the
lockups occur.
Absolutely nothing is logged in the syslog, it is a complete freeze. I
could get the system to hang by attempting to delete a 95GB tar file
from a client (over NFS), it would lock up every time. At other times
it just locks up (overnight for example).
I have had a top session running a couple of times when it locks up
and btrfs-transaction and btrfs-flush_del are using 3 to 5 cores at 50
to 100% (see top extract below).
top - 12:06:37 up 1:51, 1 user, load average: 3.33, 0.87, 0.33
Tasks: 226 total, 5 running, 221 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.0 us, 48.5 sy, 0.0 ni, 50.9 id, 0.1 wa, 0.0 hi, 0.5 si, 0.0 st
KiB Mem: 12295372 total, 12138296 used, 157076 free, 312 buffers
KiB Swap: 7831536 total, 56 used, 7831480 free, 24644 cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1005 root 20 0 0 0 0 R 100. 1 0.0 0:50.16
btrfs-transacti
2462 root 20 0 0 0 0 R 75.8 0.0 0:06.66
btrfs-flush_del
2459 root 20 0 0 0 0 S 72.5 0.0 0:10.18
btrfs-flush_del
2463 root 20 0 0 0 0 S 70.5 0.0 0:14.41
btrfs-flush_del
2457 root 20 0 0 0 0 R 38.6 0.0 0:28.35
btrfs-flush_del
2458 root 20 0 0 0 0 S 17.0 0.0 0:39.31
btrfs-flush_del
1959 root 20 0 0 0 0 R 9.6 0.0 0:31.68
btrfs-flush_del
100 root 20 0 0 0 0 S 7.6 0.0 0:00.31 kswap
I have looked in bugzilla and can't relate this to anything already
reported, has anyone seen something similar to this?
Regards
Sean
next reply other threads:[~2013-10-23 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 19:26 Sean Clarke [this message]
2013-10-23 20:05 ` 3.11 and 3.12rc continual hard lock ups Duncan
2013-10-24 8:47 ` Chris Mason
2013-10-27 9:06 ` Sean Clarke
2013-10-27 21:08 ` Sean Clarke
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='CAHCKNJj2=qfWEpWWUOBit5cJakwd+oFr1U-xj8MS-w9oQo6YQg@mail.gmail.com' \
--to=sean.clarke@sec-consulting.co.uk \
--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).