From: Chris Mason <clm@fb.com>
To: "hkbakke@gmail.com" <hkbakke@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Blocket for more than 120 seconds
Date: Mon, 16 Dec 2013 18:33:33 +0000 [thread overview]
Message-ID: <1387218823.18897.16.camel@ret.masoncoding.com> (raw)
In-Reply-To: <CAD_cGvH0p9jOB3Bm-A0Kv-b8aS=GB7DQQO9-uCa9v0ZHZgYRsQ@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1352 bytes --]
On Mon, 2013-12-16 at 19:22 +0100, Hans-Kristian Bakke wrote:
> I have explicitly set compression=lzo, and later noatime just to test
> now, else it's just default 3.12.4 options (or 3.13-rc2 when I tested
> that).
>
> To make sure, here is my btrfs mounts from /proc/mounts:
> /dev/sdl /btrfs btrfs rw,noatime,compress=lzo,space_cache 0 0
> /dev/sdl /storage/storage-vol0 btrfs rw,noatime,compress=lzo,space_cache 0 0
>
> /etc/fstab:
> UUID=9302fc8f-15c6-46e9-9217-951d7423927c /btrfs btrfs
> defaults,compress=lzo,noatime 0 2
> UUID=9302fc8f-15c6-46e9-9217-951d7423927c /storage/storage-vol0
> btrfs defaults,subvol=storage-vol0,noatime 0 2
>
> Hardware:
> CPU: Intel Xeon X3430 (Quad Core)
> MB: Supermicro X8SI6-F
> RAM: 16GB (4x4GB) Samsung ECC/Unbuffered DDR3 1333mhz CL9 (MEM-DR340L-SL01-EU13)
> HDDs in btrfs RAID10: 8 x Western Digital Se 4TB 64MB 7200RPM SATA
> 6Gb/s (WD4000F9YZ)
> HBAs: LSI SAS 9211-8i, LSI SAS 9201-16i
>
Ok, could you please capture the dmesg output after a sysrq-w during one
of the stalls during rsync writing? We want to see all the stack traces
of all the waiting procs.
Defrag is a slightly different use case, so I want to address that
separately.
-chris
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±ý»k~ÏâØ^nr¡ö¦zË\x1aëh¨èÚ&£ûàz¿äz¹Þú+Ê+zf£¢·h§~Ûiÿÿïêÿêçz_è®\x0fæj:+v¨þ)ߣøm
next prev parent reply other threads:[~2013-12-16 18:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 20:30 Blocket for more than 120 seconds Hans-Kristian Bakke
2013-12-14 21:35 ` Chris Murphy
2013-12-14 23:19 ` Hans-Kristian Bakke
2013-12-14 23:50 ` Chris Murphy
2013-12-15 0:28 ` Hans-Kristian Bakke
2013-12-15 1:59 ` Chris Murphy
2013-12-15 2:35 ` Hans-Kristian Bakke
2013-12-15 13:24 ` Duncan
2013-12-15 14:51 ` Hans-Kristian Bakke
2013-12-15 23:08 ` Duncan
2013-12-16 0:06 ` Hans-Kristian Bakke
2013-12-16 10:19 ` Duncan
2013-12-16 10:55 ` Hans-Kristian Bakke
2013-12-16 15:00 ` Duncan
2013-12-16 15:18 ` Chris Mason
2013-12-16 16:32 ` Hans-Kristian Bakke
2013-12-16 18:16 ` Chris Mason
2013-12-16 18:22 ` Hans-Kristian Bakke
2013-12-16 18:33 ` Chris Mason [this message]
2013-12-16 18:41 ` Hans-Kristian Bakke
2013-12-15 3:47 ` George Mitchell
2013-12-15 23:39 ` Charles Cazabon
2013-12-16 0:16 ` Hans-Kristian Bakke
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=1387218823.18897.16.camel@ret.masoncoding.com \
--to=clm@fb.com \
--cc=hkbakke@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).