All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Szőts Ákos" <szotsaki@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs-ino-cache runs on every boot for 6 minutes
Date: Tue, 03 Dec 2013 12:28:26 +0100	[thread overview]
Message-ID: <1531404.tFNCiHaLVH@linux-suse.hu> (raw)

Dear list members,

I'm not sure if this a bug or an intended behaviour, since I've yet to find a 
reliable source with Google search.

My problem is the following: with the 3.12 kernel on every single boot (even 
when the computer was shut down clear) the process [btrfs-ino-cache] is 
preventing the successful startup of X because it's running for 6 minutes.

I can see this in "iotop" and while that program runs the whole system is 
being blocked. After 6 minutes I restart X and everyting goes normal from that 
point on.

My question is: is that necessary to regenerate the inode cache on every boot 
or is this a bug? Of course if I remove the "inode_cache" option from fstab, 
this phenomenon disappears.

Versions:
- OS: openSUSE 13.1
- Kernel: 3.12.0-6.ge7c00d8-desktop #1 SMP PREEMPT Tue Nov 12 13:09:24 UTC 
2013 (e7c00d8)
- Mount options: compress=lzo,space_cache,inode_cache,noatime

Best regards,

Ákos

             reply	other threads:[~2013-12-03 11:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03 11:28 Szőts Ákos [this message]
2013-12-03 13:22 ` btrfs-ino-cache runs on every boot for 6 minutes Duncan
2013-12-04  2:15 ` Liu Bo
2013-12-04 12:41   ` Szőts Ákos
2013-12-06  6:04     ` Liu Bo
2013-12-06 12:46       ` Szőts Ákos
2013-12-06 13:30         ` Liu Bo
2013-12-07 14:48           ` Szőts Ákos
2013-12-05  9:14   ` Szőts Ákos

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=1531404.tFNCiHaLVH@linux-suse.hu \
    --to=szotsaki@gmail.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.