All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 27 Jun 2006 12:24:57 +0200	[thread overview]
Message-ID: <20060627122457.2cabc4d7@localhost> (raw)
In-Reply-To: <20060627095443.GQ22071@suse.de>

On Tue, 27 Jun 2006 11:54:44 +0200
Jens Axboe <axboe@suse.de> wrote:

> > So the problem is that "fcache_close_dev()" have zero chances to run ;)
> 
> Hmm, you seem to be using an older fcache version. I'll test this and
> post an updated patch if it doesn't work with the newer version.

I'm using the one that comes with "2.6.17-ck1" as the subject suggest :)

Anyway I've just seen this in your git tree:


@@ -2222,6 +2283,7 @@ static int ext3_remount (struct super_bl

[CUT]

        ext3_init_journal_params(sb, sbi->s_journal);

+       if (fcache_devnum) {
+               ext3_close_fcache(sb);
+               ext3_open_fcache(sb, fcache_devnum);
+       }


So I suppose that it's already fixed.

:)

-- 
	Paolo Ornati
	Linux 2.6.17-ck1 on x86_64

  reply	other threads:[~2006-06-27 10:25 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
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 [this message]
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=20060627122457.2cabc4d7@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.