From: Andrew Morton <akpm@zip.com.au>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Jamie Lokier <lk@tantalophile.demon.co.uk>,
"Theodore Ts'o" <tytso@mit.edu>, Brian <hiryuu@envisiongames.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andreas Dilger <adilger@turbolabs.com>
Subject: Re: File server FS?
Date: Sat, 17 Nov 2001 14:10:01 -0800 [thread overview]
Message-ID: <3BF6E039.923E0577@zip.com.au> (raw)
In-Reply-To: <200111132203.fADM3jW03006@demai05.mw.mediaone.net> <20011113175348.B24864@mikef-linux.matchmail.com> <20011117181253.B5003@kushida.jlokier.co.uk>, <20011117181253.B5003@kushida.jlokier.co.uk> <20011117135542.H21354@mikef-linux.matchmail.com>
Mike Fedyk wrote:
>
> I haven't actually resized any ext2/3 partitions. Didn't need to. I'll do
> some tests though.
I tested it a while back - it worked OK. If you could retest that'd be
neat.
The journal shouldn't be affected - it's just a regular file.
mke2fs and tune2fs choose an initial journal size based
on the size of the fs, so if you were increasing the
fs size by a large ratio then there may be a case for
increasing the journal size. But as you've pointed out,
an 8, 16 or 32 megabyte journal covers an awful lot of metadata.
next prev parent reply other threads:[~2001-11-17 22:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 22:03 Brian
2001-11-14 1:53 ` Mike Fedyk
2001-11-14 2:05 ` Sean Elble
2001-11-14 10:41 ` Robert Szentmihalyi
2001-11-14 15:10 ` Steve Lord
2001-11-14 16:09 ` Robert Szentmihalyi
2001-11-17 18:12 ` Jamie Lokier
2001-11-17 21:55 ` Mike Fedyk
2001-11-17 22:10 ` Andrew Morton [this message]
2001-11-17 22:23 ` Mike Fedyk
2001-11-17 22:31 ` Andrew Morton
2001-11-17 22:38 ` Andreas Dilger
2001-11-18 1:34 ` Jamie Lokier
2001-11-17 22:27 ` Andreas Dilger
2001-11-16 10:19 ` Pavel Machek
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=3BF6E039.923E0577@zip.com.au \
--to=akpm@zip.com.au \
--cc=adilger@turbolabs.com \
--cc=hiryuu@envisiongames.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
--cc=mfedyk@matchmail.com \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®