From: Mike Fedyk <mfedyk@matchmail.com>
To: Andrew Morton <akpm@zip.com.au>
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:23:26 -0800 [thread overview]
Message-ID: <20011117142326.I21354@mikef-linux.matchmail.com> (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> <3BF6E039.923E0577@zip.com.au>
In-Reply-To: <3BF6E039.923E0577@zip.com.au>
On Sat, Nov 17, 2001 at 02:10:01PM -0800, Andrew Morton wrote:
> 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.
>
I'll try to do that over the next couple weeks.
> The journal shouldn't be affected - it's just a regular file.
>
That's what I meant by "as long as the inode number is the same". Since it
is a normal file, the only thing ext2resize might overlook would be the
inode number for the jounal that's kept in the super block. If, in fact
ext2resize does decide to change inode numbers for some reason. I don't
know if it does.
> 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.
Yep. It would be more important for data=journal mode.
Can ext2resize change the block size too? If the journal is larger than
100MB then it would need to be made smaller for 1k blocks 200MB for 2k
blocks, and left at 400MB for 4k blocks.
Mike
next prev parent reply other threads:[~2001-11-17 22:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 22:03 File server FS? 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
2001-11-17 22:23 ` Mike Fedyk [this message]
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=20011117142326.I21354@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=adilger@turbolabs.com \
--cc=akpm@zip.com.au \
--cc=hiryuu@envisiongames.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
--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 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.