All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Brian Sullivan <bexamous@gmail.com>
Cc: Josef Bacik <josef@redhat.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: Tue, 23 Nov 2010 16:07:35 -0500	[thread overview]
Message-ID: <1290546410-sup-7975@think> (raw)
In-Reply-To: <AANLkTinSCdOcXR=9om+oiMZAQS6fOkPuW-gSUTEzkipN@mail.gmail.com>

Excerpts from Brian Sullivan's message of 2010-11-23 15:27:09 -0500:
> On Mon, Nov 22, 2010 at 4:54 PM, Chris Mason <chris.mason@oracle.com>=
 wrote:
> > Excerpts from Brian Sullivan's message of 2010-11-22 18:29:42 -0500=
:
> >> On Fri, Nov 19, 2010 at 12:09 PM, Brian Sullivan <bexamous@gmail.c=
om> wrote:
> >> > On Fri, Nov 19, 2010 at 6:46 AM, Josef Bacik <josef@redhat.com> =
wrote:
> >> >> On Fri, Nov 19, 2010 at 09:32:46AM -0500, Chris Mason wrote:
> >> >>>
> >> >>> I just wanted to confirm, you're seeing this with 2.6.37-rc? =C2=
=A0I thought
> >> >>> I had fixed up this delalloc hammering.
> >> >>>
> >> >
> >> > I installed 2.6.37-rc2 from an Ubuntu PPA.
> >> >
> >> >>
> >> >> Also can you run with this patch
> >> >>
> >> >> http://www.spinics.net/lists/linux-btrfs/msg06890.html
> >> >>
> >> >
> >> > Will try tonight.
> >> >
> >>
> >> Got 2.6.37-rc2 from kernel.org, applied this patch, and still not =
able
> >> to write to the filesystem.
> >
> > So with the patch are you still seeing the 100% system time?
> >
> > -chris
> >
>=20
> Yes, no change with patch.

Ok, the short term solution is going to be adding another drive to your
=46S and letting the space spill over to there.

I'd like to try and reproduce here though, if it isn't too difficult to
keep things in the current state?

-chris
--
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

      reply	other threads:[~2010-11-23 21:07 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
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 [this message]

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=1290546410-sup-7975@think \
    --to=chris.mason@oracle.com \
    --cc=bexamous@gmail.com \
    --cc=cjb@laptop.org \
    --cc=daniel.blueman@gmail.com \
    --cc=josef@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.