From: Dave Jones <davej@redhat.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Andrew Morton <akpm@osdl.org>,
sct@redhat.com, jack@suse.cz,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
ext2-devel <Ext2-devel@lists.sourceforge.net>
Subject: Re: [RFC PATCH] ext3 writepage() journal avoidance
Date: Fri, 10 Mar 2006 11:51:57 -0500 [thread overview]
Message-ID: <20060310165157.GD18755@redhat.com> (raw)
In-Reply-To: <1142008847.21442.17.camel@dyn9047017100.beaverton.ibm.com>
On Fri, Mar 10, 2006 at 08:40:47AM -0800, Badari Pulavarty wrote:
> > > > I don't know how much usage it's had, sorry. It's only allowed in
> > > > data=writeback mode and not many people seem to use even that.
> > >
> > > would you be prepared to turn it on by default in -mm for a bit to see
> > > how it holds up? The concept seems valuable in itself, so much so that I
> > > feel this should be 1) on always by default when possible and 2) isn't
> > > really the kind of thing that should be a long term option; not having
> > > it almost is a -o pleaseAddThisBug option for each bug fixed.
> >
> > It'd be good to get that hammered on, as it doesn't see hardly any testing
> > based upon the experiments I did sometime last year. It left me with
> > an unmountable root filesystem :-/
>
> Yuck. You are talking about "nobh" option for writeback mode, correct ?
> Have any idea on what you were doing ?
Actually, I think I may have neglected to make those mounts writeback.
In retrospect, it was silly, I basically forced nobh on for all mounts.
A few boots later my / reached its maximum mount count, and got a fsck,
which moved a bunch of useful things like /lib/ld-linux.so.2 to lost+found.
There was so much mess that it was easier to reinstall the box than
to pick through it. (Thankfully I tested it on a scratch box ;-)
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-03-10 16:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 18:39 [RFC PATCH] ext3 writepage() journal avoidance Badari Pulavarty
2006-03-09 23:22 ` Andrew Morton
2006-03-10 0:45 ` Badari Pulavarty
2006-03-10 0:45 ` Badari Pulavarty
2006-03-10 1:16 ` Andrew Morton
2006-03-10 7:59 ` Arjan van de Ven
2006-03-10 8:23 ` Andrew Morton
2006-03-10 8:23 ` Andrew Morton
2006-03-10 8:43 ` Arjan van de Ven
2006-03-10 8:53 ` Andrew Morton
2006-03-10 14:58 ` Badari Pulavarty
2006-03-10 16:19 ` Dave Jones
2006-03-10 16:19 ` Dave Jones
2006-03-10 16:40 ` Badari Pulavarty
2006-03-10 16:51 ` Dave Jones [this message]
2006-03-10 17:00 ` Badari Pulavarty
2006-03-10 16:46 ` Badari Pulavarty
2006-03-10 13:43 ` Dave Kleikamp
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=20060310165157.GD18755@redhat.com \
--to=davej@redhat.com \
--cc=Ext2-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=sct@redhat.com \
/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.