linux-ext4 - Re: Ext3 onlie resize failure due to small journal size

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 12 Jul 2007 10:40:00 +0530
From:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
To:	Andreas Dilger <adilger@...sterfs.com>
CC:	Suzuki <suzuki@...ux.vnet.ibm.com>, linux-ext4@...r.kernel.org,
	Amit K Arora <amitarora@...ibm.com>,
	Mingming Cao <cmm@...ibm.com>
Subject: Re: Ext3 onlie resize failure due to small journal size



Andreas Dilger wrote:
> 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?
> 
>

That't true. I was looking at it. I guess we should make sure we can
ask for a credit same as inode tables block per group + some extra.

Will try to see i can cook a patch.

-aneesh
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html