All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Muralitharan Perumal <muralitharan.perumal@pace.com>
Cc: xfs@oss.sgi.com
Subject: Re: kernel 2.6.22 pdflush consumes ~90% cpu
Date: Tue, 14 Jan 2014 07:56:10 +1100	[thread overview]
Message-ID: <20140113205610.GK3469@dastard> (raw)
In-Reply-To: <52D3FF2E.3010901@pace.com>

On Mon, Jan 13, 2014 at 02:58:54PM +0000, Muralitharan Perumal wrote:
> Hi,
> 
> I am currently working on an embedded platform involving XFS as the
> preferred fs. Earlier, ext3 was used but now replaced with XFS. The unit
> is working fine with ext3 but after replacing with XFS, I am seeing a
> few issues:
> 
> a) Occassionally I am getting the following error when we write files to
> the fs:
> 
> attempt to access beyond end of device
> sda1: rw=0, want=10487141907480064, limit=9766912
> I/O error in filesystem ("sda1") meta-data dev sda1 block 0x254200001abdf8       ("xfs_trans_read_buf") error 5 buf count 4096
> attempt to access beyond end of device
> sda1: rw=0, want=10487141907480064, limit=9766912
> I/O error in filesystem ("sda1") meta-data dev sda1 block 0x254200001abdf8       ("xfs_trans_read_buf") error 5 buf count 4096

It's trying to write way beyond the end of the device, hence the
error. I'd suggest updating to xfsprogs 3.11 and running
xfs_repair -n /dev/sda1 on the device and seeing if it finds a
corrupt block map on an inode somewhere.

> b) After running for about 20 to 25 minutes, the pdflush consumes about 90% cpu and stuck there in D state:

It can't be stuck in an uninterruptible sleep (D state) and
consuming CPU at the same time....

> Is there any similar issue seen with kernel 2.6.22? Am I missing any XFS patches that could fix this?

That's a 6 year old kernel. I'd suggest that an upgrade to something
more recent might be in order...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2014-01-13 20:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 14:58 kernel 2.6.22 pdflush consumes ~90% cpu Muralitharan Perumal
2014-01-13 20:32 ` Muralitharan Perumal
2014-01-13 20:50 ` Eric Sandeen
2014-01-13 20:56 ` Dave Chinner [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=20140113205610.GK3469@dastard \
    --to=david@fromorbit.com \
    --cc=muralitharan.perumal@pace.com \
    --cc=xfs@oss.sgi.com \
    /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.