linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: Brian Sullivan <bexamous@gmail.com>,
	Daniel J Blueman <daniel.blueman@gmail.com>,
	Chris Ball <cjb@laptop.org>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: ls & flush-btrfs-1 sit at 100% sys
Date: Fri, 19 Nov 2010 09:46:25 -0500	[thread overview]
Message-ID: <20101119144625.GB2579@localhost.localdomain> (raw)
In-Reply-To: <1290177036-sup-2385@think>

On Fri, Nov 19, 2010 at 09:32:46AM -0500, Chris Mason wrote:
> Excerpts from Brian Sullivan's message of 2010-11-18 13:30:51 -0500:
> > Yep actually, with noatime,nodiratime ls is fine.  I didn't try ro but
> > I assume that'll work too.  So with noatime,nodiratime I can go around
> > in tree and ls works.  If I try to touch a new file, touch doesn't
> > return.  If I then ls in that same folder ls doesn't return either.
> > So yeah seems like soon as something has to write.
> > 
> > Also after I run touch, it doesn't return, I look at top, nothing is
> > spinning, everything is at 0% usage.  After a minute or so then touch
> > and flush-btrfs-1 jump to 50%sys each and sit there.
> 
> So, based on this trace we're banging on the delalloc flushing to free
> up room.
> 
> I just wanted to confirm, you're seeing this with 2.6.37-rc?  I thought
> I had fixed up this delalloc hammering.
> 

Also can you run with this patch

http://www.spinics.net/lists/linux-btrfs/msg06890.html

its a crap bug which will make us look like we're out of space when we arent and
we'll flush alot more.  Thanks,

Josef

  reply	other threads:[~2010-11-19 14:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18  5:03 ls & flush-btrfs-1 sit at 100% sys Brian Sullivan
2010-11-18  5:15 ` Chris Ball
2010-11-18  6:03   ` Brian Sullivan
2010-11-18 11:08     ` Daniel J Blueman
2010-11-18 18:30       ` Brian Sullivan
2010-11-19 14:32         ` Chris Mason
2010-11-19 14:46           ` Josef Bacik [this message]
2010-11-19 20:09             ` Brian Sullivan
2010-11-22 23:29               ` Brian Sullivan
2010-11-23  0:54                 ` Chris Mason
2010-11-23 20:27                   ` Brian Sullivan
2010-11-23 21:07                     ` Chris Mason

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=20101119144625.GB2579@localhost.localdomain \
    --to=josef@redhat.com \
    --cc=bexamous@gmail.com \
    --cc=chris.mason@oracle.com \
    --cc=cjb@laptop.org \
    --cc=daniel.blueman@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).