From: Jens Axboe <axboe@suse.de>
To: Paolo Ornati <ornati@fastwebnet.it>
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 15:35:45 +0200 [thread overview]
Message-ID: <20060627133544.GW22071@suse.de> (raw)
In-Reply-To: <20060627153043.60582710@localhost>
On Tue, Jun 27 2006, Paolo Ornati wrote:
> On Tue, 27 Jun 2006 15:10:33 +0200
> Jens Axboe <axboe@suse.de> wrote:
>
> > > Cannot the code figure out this himself al let "mount -o remount,ro"
> > > work?
> >
> > It could be fixed up, yes, but for now you have to always pass the fdev
> > option for it to work. Sorry, I thought you knew that, I think I wrote
> > that in the original mail as well.
>
> No ;)
>
> http://lkml.org/lkml/2006/5/15/46
>
> you talked about remounting rw at boot (modifing distro script) and
> remounting for stopping priming.
I guess not, I've not noticed since my modified suse boot.rootfs script
use FCACHE_ARGS for both mount rw and remount ro. I does tell you to use
fdev for rw remounts though, so it's not like I didn't hint at it at
least :-)
> > But it needs to be fixed of course, also so you don't have to do it for
> > 'rw' remounts (which I sometimes do just to check stats).
>
> I agree :)
Will fix it up, for now just pass fdev= always.
--
Jens Axboe
next prev parent reply other threads:[~2006-06-27 13:34 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
2006-06-27 13:10 ` Jens Axboe
2006-06-27 13:30 ` Paolo Ornati
2006-06-27 13:35 ` Jens Axboe [this message]
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=20060627133544.GW22071@suse.de \
--to=axboe@suse.de \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ornati@fastwebnet.it \
/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.