From: youagree <n3ocort3x@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Applications using fsync cause hangs for several seconds every few minutes
Date: Thu, 18 Aug 2011 09:55:56 +0200 [thread overview]
Message-ID: <j2igev$9nk$1@dough.gmane.org> (raw)
In-Reply-To: <4E4CBF43.60207@uvm.edu>
On 08/18/2011 09:29 AM, Andrew Guertin wrote:
> * Many processes occasionally hang for a short time
> * When this happens, my cpu monitor shows a short burst of cpu activity
> (100% of 1 core) followed by a longer period of IO
> * When this happens, iotop shows [btrfs-submit-0] and [btrfs-transacti]
> at the top of the list
> * Behavior slowly increases in duration (and frequency?) over time, and
> goes away with a reboot
> * Heavy IO makes behavior appear faster
>
> ... and the following behaviors before commit 4e69b59:
>
> * Occasional spikes of IO on cpu monitor concurrent with
> [btrfs-submit-0] and [btrfs-transacti] at top of iotop
> * No hangs, even when that occurs
Yes, exactly that happened in my case too. Yours is a much more precise
description! I did not diagnose 2.6.38 further because I just wanted to
establish a known-good version and at first sight (2 days uptime) my HDD
behavior showed that it cannot be good if _any_ HDD thrashing appears at
all in the first place...
I was able to work with the computer during those IO spikes on 2.6.38
too, although it was observable that the HDD is being thrased
(meanwhile, LED was almost constant lit). But it didn't cause other
programs to be unresponsive, I confirm...
> I wasn't taking notes or anything though, so I'm not 100% certain I was
> observing or interpreting or remembering everything correctly.
>
> --Andrew
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-08-18 7:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 21:29 Applications using fsync cause hangs for several seconds every few minutes Andrew Guertin
2011-08-12 1:13 ` Andrew Guertin
2011-08-18 14:38 ` Chris Mason
2011-08-20 17:18 ` Andrew Guertin
2011-08-17 14:24 ` Andrew Guertin
2011-08-17 14:29 ` Michael Cronenworth
2011-08-17 14:38 ` Andrew Guertin
2011-08-17 14:55 ` Dave
2011-08-18 2:41 ` Anand Jain
2011-08-18 6:44 ` youagree
2011-08-18 7:29 ` Andrew Guertin
2011-08-18 7:55 ` youagree [this message]
2011-08-18 11:45 ` Andrew Guertin
2011-08-19 9:58 ` Anand Jain
2011-08-18 7:41 ` Andrew Guertin
2011-08-18 6:47 ` Chris Samuel
2011-08-18 6:58 ` youagree
2011-08-19 7:34 ` Chris Samuel
-- strict thread matches above, loose matches on Subject: below --
2011-06-21 11:15 Jan Stilow
2011-06-06 22:58 Nirbheek Chauhan
2011-07-18 17:37 ` Mck
2011-07-18 18:17 ` Josef Bacik
2011-07-20 20:59 ` Nirbheek Chauhan
2011-08-03 15:50 ` mck
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='j2igev$9nk$1@dough.gmane.org' \
--to=n3ocort3x@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).