From: Paolo Ornati <ornati@fastwebnet.it>
To: Jens Axboe <axboe@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ck@vds.kolivas.org
Subject: Re: 2.6.17-ck1: fcache problem...
Date: Sun, 25 Jun 2006 15:23:25 +0200 [thread overview]
Message-ID: <20060625152325.605faf1f@localhost> (raw)
In-Reply-To: <20060625102837.GC20702@suse.de>
On Sun, 25 Jun 2006 12:28:39 +0200
Jens Axboe <axboe@suse.de> wrote:
> > [ 26.673525] fcache: found serial 33, expected 34.
> > [ 26.673529] fcache: reprime the cache!
> > [ 26.673535] ext3: failed to open fcache (err=-22)
>
> Hmm, and you are sure that the fs is properly umounted on reboot? Or is
> it just remounted ro? It looks like fcache_close_dev() isn't being
> called, so the cache serial doesn't match what we expect from the fs,
> hence fcache bails out since it could indicate that the fs has been
> changed without fcache being attached.
Ahh... it is the root fs and it's just remounted read-only by the
standard Gentoo scripts ;)
I don't think that unmounting it is trivial (you need to chroot to a
virtual FS or something...). Does any distro do it?
>
> What kind of speedup did you see?
with cold caches...
NORMAL
from Grub to KDM login 42"5 (~6" to reach init)
KDE 3.5.3 startup 10"
Firefox 7"
FCACHE
from Grub to KDM login 31"4 (~6" to reach init)
KDE 3.5.3 startup 4"
Firefox 2"4
:)
--
Paolo Ornati
Linux 2.6.17.1 on x86_64
next prev parent reply other threads:[~2006-06-25 13:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 7:35 2.6.17-ck1: fcache problem Paolo Ornati
2006-06-25 10:28 ` Jens Axboe
2006-06-25 13:23 ` Paolo Ornati [this message]
2006-06-25 17:43 ` Jens Axboe
2006-06-27 9:21 ` Paolo Ornati
2006-06-27 9:54 ` Jens Axboe
2006-06-27 10:24 ` Paolo Ornati
2006-06-27 13:04 ` Paolo Ornati
2006-06-27 13:10 ` Jens Axboe
2006-06-27 13:30 ` Paolo Ornati
2006-06-27 13:35 ` Jens Axboe
2006-06-27 14:20 ` Paolo Ornati
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=20060625152325.605faf1f@localhost \
--to=ornati@fastwebnet.it \
--cc=axboe@suse.de \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@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.