linux-ext4 - Re: [PATCH 2/8] e2fsprogs: Add big

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-next>] [day] [month] [year] [list]

Message-Id: <3E370776-8EA9-445D-8366-4975AD1FA57C@dilger.ca>
Date:	Mon, 21 Jun 2010 12:21:52 -0600
From:	Andreas Dilger <adilger@...ger.ca>
To:	Amir Goldstein <amir73il@...rs.sf.net>
Cc:	"linux-ext4@...r.kernel.org development" <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH 2/8] e2fsprogs: Add big_journal feature for Next3

> Next3 transactions reserve up to 24 times more credits than Ext3 transactions for the same operation.  On mke2fs and tune2fs, if the 'big_journal' feature is set along with the 'has_journal' feature, increase the default journal size by a factor of 24.

It is already possible to specify an arbitrary journal size with "-J size={MB}", so there is no need to consume a feature flag just to hint what the journal size should be.

It would be possible to check for some other snapshot-related feature flag, like "EXCLUDE_INODE" to determine if the journal is large enough for snapshotting, if it was deleted by e2fsck.  Otherwise, it is best to let the user specify the journal size they want.

Cheers, Andreas

--
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