From: Ricardo Galli <gallir@uib.es>
To: linux-kernel@vger.kernel.org
Subject: 2.6: XFS spins up the disk very often
Date: Wed, 13 Aug 2003 23:44:49 +0200 [thread overview]
Message-ID: <200308132344.49297.gallir@uib.es> (raw)
Sorry if there is a list for these XFS issues...
Since I started with 2.5 in my laptop, I noticed that the disk with XFS was
spinning up continously. I checked with vmstats, and I saw I/O almost every
60 seconds. They were mainly outputs, among 11 and 250 blocks each time.
I checked every process and redirected all syslogd to /dev/tty7 to be sure no
processes were generating the I/O. I could find none.
So finally I repartitioned the disk and copied the whole system to a XFS
partition and to an Ext3. Then I tested both, rebooting each time and
changing the root fs.
With Ext3 there is no problem, the disk spins off very rapidly, but XFS kept
doint I/O's.
So I checked it again in 2.4.21-ac4. Although there were more XFS I/O than
with Ext3, they were not so frequent as in 2.6.
I also played echoing different values to /proc/sys/fs/xfs/ and
/proc/sys/vm/pagebuf/ files without noticeable changes.
Is it a problem in 2.6 or the /proc parameters must be fine tuned?
--
ricardo galli GPG id C8114D34
http://mnm.uib.es/~gallir/
reply other threads:[~2003-08-13 21:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200308132344.49297.gallir@uib.es \
--to=gallir@uib.es \
--cc=linux-kernel@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).