linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tomáš Pružina" <pruzinat@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Fwd: [suggestion] Add verbose notification about inode-cache rebuild to kernel log
Date: Thu, 8 May 2014 16:22:13 +0200	[thread overview]
Message-ID: <CACHxQ2sQH96Z==zqEaoEoOxc65k9TYD66yLXQzOYL1kxaPcrqw@mail.gmail.com> (raw)
In-Reply-To: <CACHxQ2tAU15z_pUEGBuGqYFR9n_fH9BeyA8=jYryRrb3H=zCYA@mail.gmail.com>

Good day,
I ran into some troubles with inode-cache rebuilding on root fs after
filesystem was mounted without inode_cache, which stalls boot of my
box by several minutes.

I boot from commandline like:
root=/dev/sda4 rootfstype=btrfs
rootflags=inode_cache,space_cache,autodefrag rw ...

However when I manually remount root fs without inode_cache (for
example via kexec), it triggers cache rebuild at next mount which
takes several tens of minutes and mimick 'freeze' on boot.

Would it be possible to put some printk saying that this is happening
so users don't get confused about it??

Thanks.

       reply	other threads:[~2014-05-08 14:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACHxQ2tAU15z_pUEGBuGqYFR9n_fH9BeyA8=jYryRrb3H=zCYA@mail.gmail.com>
2014-05-08 14:22 ` Tomáš Pružina [this message]
2014-05-09 14:51   ` Fwd: [suggestion] Add verbose notification about inode-cache rebuild to kernel log David Sterba
2014-05-09 18:12     ` Goffredo Baroncelli
2014-05-12 14:39       ` David Sterba
2014-05-12 18:18         ` Goffredo Baroncelli
2014-05-13  4:55           ` Duncan
2014-05-13 14:22           ` David Sterba

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='CACHxQ2sQH96Z==zqEaoEoOxc65k9TYD66yLXQzOYL1kxaPcrqw@mail.gmail.com' \
    --to=pruzinat@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 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).