From: Josef Bacik <jbacik@fusionio.com>
To: dima <dolenin@parallels.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-ino-cache is running on each reboot
Date: Tue, 13 Aug 2013 11:37:19 -0400 [thread overview]
Message-ID: <20130813153719.GH2150@localhost.localdomain> (raw)
In-Reply-To: <52098BDB.5010400@parallels.com>
On Tue, Aug 13, 2013 at 10:28:59AM +0900, dima wrote:
> Hello all,
>
> About a week or so ago I noticed that [btrfs-ino-cache] process was
> appearing in the 'top' on each reboot and disk is spinning like crazy for
> about five minutes or so. Quite so often this caused X failing to start
> because all I/O was busy with caching.
> Even after letting it to calm down and seeing [btrfs-ino-cache] disappearing
> from the process list, on next reboot it starts all over again.
>
> Here is the fstab entry that I have
>
> UUID=430dca92-9541-4201-0f62-373e30beadac / btrfs subvol=root_subvolume,defaults,noatime,noacl,compress=lzo,inode_cache,space_cache,autodefrag
> 0 0
>
> inode_cache was always enabled since the FS was created about a year or so
> ago, and actually I have never had any problems with it up until recently.
>
> Removing inode_cache option from fstab solves the problem, but I am not sure
> if it is the right choice.
> I can observe the problem at least in the vanilla kernel 3.10.4 ~ 6 (did not
> try older versions)
>
> What could be the reason for such behavior and how to avoid it?
>
That's odd. Can you apply patches and build kernels so I can try and narrow
down what is happening? Thanks,
Josef
next prev parent reply other threads:[~2013-08-13 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 1:28 btrfs-ino-cache is running on each reboot dima
2013-08-13 4:09 ` Duncan
2013-08-13 5:37 ` dima
2013-08-13 15:37 ` Josef Bacik [this message]
2013-08-14 1:17 ` dima
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=20130813153719.GH2150@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=dolenin@parallels.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.