From: "Szőts Ákos" <szotsaki@gmail.com>
To: bo.li.liu@oracle.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-ino-cache runs on every boot for 6 minutes
Date: Fri, 06 Dec 2013 13:46:10 +0100 [thread overview]
Message-ID: <14005207.4jWyJLzXAX@linux-suse.hu> (raw)
In-Reply-To: <20131206060419.GA20595@localhost.localdomain>
A következőt írtad ekkor: 2013. december 6. 14:04:19
> Could you please try the following and show me the output of dmesg?
>
> thanks,
> -liubo
The following happened:
- I upgraded to 3.13.0-rc2-6.ge7c00d8 (since the original 3.12 kernel with
SUSE patches is not available anymore)
- Patched it and booted from that, compiled the NVIDIA driver
- and suddenly everything started to work fine. Now I don't have to wait 6
minutes for the [btrfs-ino-cache] process.
One thing I noticed: before any logging would start, kernel prints out some
(initramfs?) messages, like:
"Waiting for device /dev/disk/... to appear
[...]
fsck succeeded Mounting root read-write
Mounting root /dev/disk/...
mount -o rw,compress=lzo,space_cache,noatime,inode_cache /dev/... /root"
And logging starts from this point.
The interesting point is the initramfs mounting options: with the stock 3.12
kernel I had only the following: rw,compress=lzo,space_cache. But now it's
rw,compress=lzo,space_cache,noatime,inode_cache. In /etc/fstab the options are
intact for a month now. Maybe I should have regenerated the initrd when I
added the fstab mount options noatime and inode_cache?
I searched for your extra kernel messages in dmesg, but I didn't find them,
although here is the dmesg output: http://paste.opensuse.org/30797527
Thank you,
Ákos
next prev parent reply other threads:[~2013-12-06 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 11:28 btrfs-ino-cache runs on every boot for 6 minutes Szőts Ákos
2013-12-03 13:22 ` 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 [this message]
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=14005207.4jWyJLzXAX@linux-suse.hu \
--to=szotsaki@gmail.com \
--cc=bo.li.liu@oracle.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).