All of lore.kernel.org
 help / color / mirror / Atom feed
From: dima <dolenin@parallels.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-ino-cache is running on each reboot
Date: Tue, 13 Aug 2013 14:37:30 +0900	[thread overview]
Message-ID: <5209C61A.5010702@parallels.com> (raw)
In-Reply-To: <pan$9b25b$c3cfd854$ecd09a4$c58fb9da@cox.net>

On 08/13/2013 01:09 PM, Duncan wrote:
> dima posted on Tue, 13 Aug 2013 10:28:59 +0900 as excerpted:
>
>> 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.
>
>> 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.
>
> A number of people have reported problems with inode_cache enabled, and
> the recommendation has always been to turn it off "unless you need it".
> Easy enough problem to fix, I guess. =:^)
>
> Of course that immediately invites the question of why have the option at
> all if all it does is cause trouble, and (as a user not a dev) I don't
> have the answer to that.  I don't know the use case when "unless you need
> it" would actually apply, but apparently, it does in some cases.
>
> I guess the wiki[1] should really have a warning on that option, but
> without a more solid reason than "just don't turn it on, causes more
> trouble than it's worth", I'd feel kind of goofy adding it.
>
> Anyway, yes, the general recommendation on the list at this point seems
> to be to simply leave inode_cache off and not worry about it.


Thanks Duncan. So I did.
I was just wondering why it stopped behaving all of a sudden.



> ---
> [1] https://btrfs.wiki.kernel.org/
>

  reply	other threads:[~2013-08-13  5: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 [this message]
2013-08-13 15:37 ` Josef Bacik
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=5209C61A.5010702@parallels.com \
    --to=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.