From: Shridhar Daithankar <ghodechhap@ghodechhap.net>
To: linux-btrfs@vger.kernel.org
Subject: inode cache rebuild problem
Date: Wed, 23 Apr 2014 23:07:13 +0630 [thread overview]
Message-ID: <2497757.A2A0fxBM0J@bheem> (raw)
Hello,
I have a desktop system with 2 disks, all btrfs, single partition. All of
these partitions had
space_cache,inode_cache enabled.
Linux 3.14 has broken resume on my desktop, hence I need to shutdown and
restart the
machine every time.
But even on clean reboot, inode_cache was constantly being rebuilt on each
boot. It
caused kdm/X to timeout, even getty weren't spawned. I had to reboot it with
ctrl-alt-delete,
just to make it usable again. 2 out of 3 times, I had to reboot more than
once, to make it
usable.
While the disk was constantly grinding in the boot process, I ssh'ed into it
from another
machine and observed the inode cache overhead.
Hence I disabled both the caches on all the partition(yes, I know, space_cache
will stick
around), and the machine is lot more snappier and responsive than ever before.
I am running archlinux with 3.14.1 kernel.
Thanks,
--
Regards
Shridhar
next reply other threads:[~2014-04-23 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 16:37 Shridhar Daithankar [this message]
2014-04-24 10:32 ` inode cache rebuild problem Duncan
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=2497757.A2A0fxBM0J@bheem \
--to=ghodechhap@ghodechhap.net \
--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 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).