All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Andrea Gelmini <andrea.gelmini@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: different oops
Date: Tue, 07 Oct 2008 08:56:33 -0400	[thread overview]
Message-ID: <1223384193.16546.111.camel@think.oraclecorp.com> (raw)
In-Reply-To: <9cdbb57f0810070431w523f90eek63fd74e44add35cd@mail.gmail.com>

On Tue, 2008-10-07 at 13:31 +0200, Andrea Gelmini wrote:
> 2008/10/4 Chris Mason <chris.mason@oracle.com>:
> >> I'm going to try to use the cloned partition as my new /.
> >> Is there something dangerous other the ENOSPC?
> >
> > We don't have known big bugs right now, but you'll need to use another
> > FS on /boot.
> 
> I use initd, so no problem.
> Anyway, I started using btrfs for my /home (before it was Reiserfs3).
> Well, after few days of usage, the good news is about no problem like
> crash, file corruption, and so on. It also worked well with TuxOnIce,
> with a lot of suspend/resume cycle. The bad news is about load
> average. In normal session (WindowMaker, Firefox, Kopete, Skype,
> Konsole, Evince, Azureus, Evolution, K3B) I've a lot higher load
> average respect Reiserfs3. The worst is using mirrordir to backup
> /home on external device (load avg > 10).
> Is it a normal work in progress, or does it happens only to me?
> My /home is over dm-crypt, by the way.
> 

Btrfs does use more cpu than reiserfs will because of the checksumming,
and you have dm-crypt using CPU as well.  Is the system unresponsive
during the high load?

The load on linux is somewhat strange because it reflects both the
number of procs waiting on IO and the number using CPU.  Running top and
looking at the process states will help figure out which one is the
cause 'D' means IO and 'R' means CPU.

-chris



  reply	other threads:[~2008-10-07 12:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-03 16:14 different oops Martin Bürger
2008-10-03 16:40 ` Chris Mason
2008-10-03 17:10   ` Martin Bürger
2008-10-03 19:07     ` Chris Mason
2008-10-03 17:16   ` Andrea Gelmini
2008-10-03 17:59     ` Chris Mason
2008-10-03 18:03       ` Andrea Gelmini
2008-10-03 20:22 ` Martin Bürger
2008-10-03 20:26   ` Chris Mason
2008-10-03 22:09     ` Andrea Gelmini
2008-10-04  0:15       ` Andrea Gelmini
2008-10-04  0:30         ` Chris Mason
2008-10-04  0:31       ` Chris Mason
2008-10-04  3:41         ` Jeff Schroeder
2008-10-04 17:27           ` Chris Mason
2008-10-07 11:31         ` Andrea Gelmini
2008-10-07 12:56           ` Chris Mason [this message]
2008-10-07 15:04             ` Andrea Gelmini
2008-10-07 16:03               ` Chris Mason
2008-10-07 16:36                 ` Andrea Gelmini
2008-10-08 21:51                   ` Andrea Gelmini
2008-10-09  0:11                     ` Chris Mason
     [not found]                       ` <9cdbb57f0810090120v6381ab0eg5377039b0065e68@mail.gmail.com>
     [not found]                         ` <1223575532.14090.39.camel@think.oraclecorp.com>
2008-10-10  8:43                           ` Andrea Gelmini
     [not found]                           ` <48EE6B50.6090102@oracle.com>
2008-10-10  8:45                             ` Andrea Gelmini
2008-10-10 10:49                               ` Andrea Gelmini

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=1223384193.16546.111.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=andrea.gelmini@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 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.