All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Ornati <ornati@fastwebnet.it>
To: Paolo Ornati <ornati@fastwebnet.it>
Cc: Jens Axboe <axboe@suse.de>,
	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 15:04:40 +0200	[thread overview]
Message-ID: <20060627150440.0aaf07e1@localhost> (raw)
In-Reply-To: <20060627122457.2cabc4d7@localhost>

On Tue, 27 Jun 2006 12:24:57 +0200
Paolo Ornati <ornati@fastwebnet.it> wrote:

> So I suppose that it's already fixed.
> 
> :)

Oppss... even with your GIT tree it doesn't work :(

But this time I think I've found the problem:

--- fs/ext3/super.c ---

ext3_remount()
{
...
	unsigned long fcache_devnum = 0;
...
	if (!parse_options(data, sb, NULL, NULL, &fcache_devnum, &n_blocks_count, 1))
...
        if (fcache_devnum) {
                ext3_close_fcache(sb);
                ext3_open_fcache(sb, fcache_devnum);
        }
...
}

---------------------


If I understand correctly I have to pass the "fdev=..." option not only
when remounting "rw" but even when remounting "ro" before shutdown or
reboot.

Cannot the code figure out this himself al let "mount -o remount,ro"
work?

-- 
	Paolo Ornati
	Linux 2.6.17-gd2581eb4 on x86_64

  reply	other threads:[~2006-06-27 13:04 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
2006-06-27 13:04             ` Paolo Ornati [this message]
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=20060627150440.0aaf07e1@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.