From: Eric Sandeen <sandeen@sandeen.net>
To: Muralitharan Perumal <muralitharan.perumal@pace.com>, xfs@oss.sgi.com
Subject: Re: kernel 2.6.22 pdflush consumes ~90% cpu
Date: Mon, 13 Jan 2014 14:50:00 -0600 [thread overview]
Message-ID: <52D45178.7020009@sandeen.net> (raw)
In-Reply-To: <52D3FF2E.3010901@pace.com>
On 1/13/14, 8:58 AM, 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 7 year old kernel on an embedded platform? Nobody here will be able
to spend much time on this I'm afraid.
> 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
looks like on-disk corruption. xfs_repair is probably warranted.
> b) After running for about 20 to 25 minutes, the pdflush consumes about 90% cpu and stuck there in D state:
do a sysrq-w to get backtraces of all blocked tasks, and that might yield a clue for you.
-Eric
> Is there any similar issue seen with kernel 2.6.22? Am I missing any XFS patches that could fix this?
>
> Any pointers would be helpful.
>
> Thanks,
> Murali
>
>
> IMPORTANT NOTICE - this e-mail and any attachments hereto are strictly confidential and intended solely for the addressee. If you are not the intended recipient, please notify the sender to report the error and delete this communication immediately. You must not disclose, forward or copy this e-mail or any attachments hereto without the prior consent of the sender.
>
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-01-13 20:50 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 [this message]
2014-01-13 20:56 ` Dave Chinner
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=52D45178.7020009@sandeen.net \
--to=sandeen@sandeen.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox