Hi,
This is a follow-up to my previous message. The bug is also present in ext3,
and applies to partitions with 2K blocks and (at least in part) to those
with 4K blocks. There is also another issue, which may well be a bug in
e2fsck.
For partitions with 2K blocks the maximum file size is 275
On Wed, 06 Jun 2007 09:56:10 +0200
Laurent Vivier <[EMAIL PROTECTED]> wrote:
> Jose R. Santos wrote:
> > Set the journals JBD2_FEATURE_INCOMPAT_64BIT on devices with more
> > than 32bit block sizes during mount time. This ensure proper record
> > lenth when writing to the journal.
> >
> > Signed
On Wed, Jun 06, 2007 at 03:32:27PM +0530, Aneesh Kumar K.V wrote:
>
> If we allow to change the block size in between that would mean the
> records that we store in the tdb database will be of variable size (
> different block sizes). That would also add all the code/complexity that
> i have in
Theodore Tso wrote:
On Tue, May 22, 2007 at 03:47:33PM +0530, Aneesh Kumar K.V wrote:
This I/O manager saves the contents of the location being overwritten
to a tdb database. This helps in undoing the changes done to the
file system.
+ /* loop through the existing entries and find if th
ext4_reserve_local, ext4_rebalance_reservation, and
ext4_reserve_global are all local to balloc.c and can be made
static.
This is against the 2.6.22-rc4-ext4-1 tree that was announced
on:
http://lists.openwall.net/linux-ext4/2007/06/05/15
Signed-off-by: Kirk True <[EMAIL PROTECTED]>
Index:
Jose R. Santos wrote:
> Set the journals JBD2_FEATURE_INCOMPAT_64BIT on devices with more
> than 32bit block sizes during mount time. This ensure proper record
> lenth when writing to the journal.
>
> Signed-off-by: Jose R. Santos <[EMAIL PROTECTED]>
> Signed-off-by: Andreas Dilger <[EMAIL PROTEC
