From: Andreas Dilger <adilger@clusterfs.com>
To: Suzuki <suzuki@linux.vnet.ibm.com>
Cc: aneesh.kumar@linux.vnet.ibm.com, linux-ext4@vger.kernel.org,
Amit K Arora <amitarora@in.ibm.com>,
Mingming Cao <cmm@us.ibm.com>
Subject: Re: Ext3 onlie resize failure due to small journal size
Date: Wed, 11 Jul 2007 11:38:21 -0600 [thread overview]
Message-ID: <20070711173821.GA5495@schatzie.adilger.int> (raw)
In-Reply-To: <4694E279.1060107@linux.vnet.ibm.com>
On Jul 11, 2007 19:30 +0530, Suzuki wrote:
> Trying to resize a mounted ext3 filesystem fails due to small journal size.
>
> Background :
>
> The filesystem was created with default values, except blocksize = 4K on
> a LV partition. Later we tried extended the partition to +16M and tried
> to resize the fs using resize2fs, while it was mounted.
>
> While adding the new blockgroup, inside setup_new_group_blocks() we hit
> the limit because we are requesting for a a credit value of 2 +
> sbi->s_itb_per_group which in the case of the file system below is 1026
> while the max_transaction credits possible is 1024 for the fs.
>
> journal->j_maxlen = inode->i_size / blocksize = 16M/4K = 4K
>
> journal->j_max_transaction_buffers = journal->j_maxlen / 4 = 1K
>
> journal->j_max_transaction_buffers = 1024.
>
> Is this a supported operation ? If yes, what could be the best way to
> fix it ?
>
> Resizing the journal is not supported at the moment :(.
You can't do a journal resize online, but you can wait until your next
outage and resize the journal at that time. Even a few extra blocks
would be enough. I guess this is a corner case that hasn't been hit
before. It might make sense to have the ext2fs_figure_journal_size()
take this into account when making the filesystem?
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2007-07-12 5:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 14:00 Ext3 onlie resize failure due to small journal size Suzuki
2007-07-11 17:38 ` Andreas Dilger [this message]
2007-07-12 5:10 ` Aneesh Kumar K.V
2007-07-11 19:47 ` Kalpak Shah
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=20070711173821.GA5495@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=amitarora@in.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=suzuki@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).