linux.git/fs/ext4, branch v2.6.26-rc7

ext4: enable barriers by default

2008-05-26T16:29:46+00:00

I can't think of any valid reason for ext4 to not use barriers when
they are available;  I believe this is necessary for filesystem
integrity in the face of a volatile write cache on storage.

An administrator who trusts that the cache is sufficiently battery-
backed (and power supplies are sufficiently redundant, etc...)
can always turn it back off again.

SuSE has carried such a patch for ext3 for quite some time now.

Also document the mount option while we're at it.

Signed-off-by: Eric Sandeen 
Signed-off-by: Mingming Cao 
Signed-off-by: "Theodore Ts'o"

ext4: Display the journal_async_commit mount option in /proc/mounts

2008-05-26T14:28:28+00:00

Cc: Andreas Dilger 
Cc: Girish Shilamkar 
Signed-off-by: "Theodore Ts'o"

jbd2: If a journal checksum error is detected, propagate the error to ext4

2008-06-06T21:50:40+00:00

If a journal checksum error is detected, the ext4 filesystem will call
ext4_error(), and the mount will either continue, become a read-only
mount, or cause a kernel panic based on the superblock flags
indicating the user's preference of what to do in case of filesystem
corruption being detected.

Signed-off-by: "Theodore Ts'o"

ext4: fix online resize bug

2008-06-06T22:05:52+00:00

There is a bug when we are trying to verify that the reserve inode's
double indirect blocks point back to the primary gdt blocks.  The fix is
obvious, we need to mod the gdb count by the addr's per block.  This was
verified using the same testcase as with the ext3 equivalent of this
patch.

Signed-off-by: Josef Bacik 
Signed-off-by: Mingming Cao 
Signed-off-by: "Theodore Ts'o"

ext4: Fix uninit block group initialization with FLEX_BG

2008-06-03T18:07:29+00:00

With FLEX_BG block bitmaps, inode bitmaps and inode tables _MAY_ be
allocated outside the group.  So, when initializing an uninitialized
block bitmap, we need to check the location of this blocks before
setting the corresponding bits in the block bitmap of the newly
initialized group.  Also return the right number of free blocks when
counting the available free blocks in uninit group.

Tested-by: Aneesh Kumar K.V 
Signed-off-by: Jose R. Santos 
Signed-off-by: Mingming Cao 
Signed-off-by: "Theodore Ts'o"

ext4: Fix use of uninitialized data with debug enabled.

2008-06-06T00:59:29+00:00

Fix use of uninitialized data with debug enabled.

Signed-off-by: Aneesh Kumar K.V 
Signed-off-by: Mingming Cao 
Signed-off-by: "Theodore Ts'o"

ext4: Retry block allocation if new blocks are allocated from system zone.

2008-05-15T18:43:20+00:00

If the block allocator gets blocks out of system zone ext4 calls
ext4_error. But if the file system is mounted with errors=continue
retry block allocation. We need to mark the system zone blocks as
in use to make sure retry don't pick them again

System zone is the block range mapping block bitmap, inode bitmap and inode
table.

Signed-off-by: Aneesh Kumar K.V 
Signed-off-by: Mingming Cao 
Signed-off-by: "Theodore Ts'o"

ext4: mballoc fix mb_normalize_request algorithm for 1KB block size filesystems

2008-05-13T23:31:14+00:00

In case of inode preallocation, the number of blocks to allocate depends
on the file size and it is calculated in ext4_mb_normalize_request().
Each group in the filesystem is then checked to find one that can be
used for allocation; this is done in ext4_mb_good_group().

When a file bigger than 4MB is created, the requested number of blocks
to preallocate, calculated by ext4_mb_normalize_request is 4096.
However for a filesystem with 1KB block size, the maximum size of the
block buddies used by the multiblock allocator is 2048, so none of
groups in the filesystem satisfies the search criteria in
ext4_mb_good_group(). Scanning all the filesystem groups impacts
performance.

This was demonstrated by using a freshly created, 70GB, 1k block
filesystem, with caches dropped write before the test via
/proc/sys/vm/drop_caches, and with the filesystem mounted with
nodelalloc and nodealloc,nomballoc.  The time to write an 8 megabyte
file using "dd if=/dev/zero of=/mnt/test/fo bs=8k count=1k conv=fsync"
took 35.5091 seconds (236kB/s) with nodellaloc, and 0.233754 seconds
(35.9 MB/s) with the nodelloc,nomballoc options.  With a 1TB partition,
it took several minutes to write 8MB!

This patch modifies the algorithm in ext4_mb_normalize_group_request to
calculate the number of blocks to allocate by taking into account the
maximum size of free blocks chunks handled by the multiblock allocator.

It has also been tested for filesystems with 2KB and 4KB block sizes to
ensure that those cases don't regress.

Reviewed-by: Aneesh Kumar K.V 
Signed-off-by: Valerie Clement 
Signed-off-by: Mingming Cao 
Signed-off-by: "Theodore Ts'o"

ext4: fix typos in messages and comments (journalled -> journaled)

2008-05-14T01:27:55+00:00

Cc: 
Signed-off-by: Jan Kara 
Signed-off-by: Andrew Morton 
Signed-off-by: Mingming Cao 
Signed-off-by: "Theodore Ts'o"

ext4: fix synchronization of quota files in journal=data mode

2008-05-13T23:11:51+00:00

In journal=data mode, it is not enough to do write_inode_now as done in
vfs_quota_on() to write all data to their final location (which is
needed for quota_read to work correctly).  Calling journal_flush() does
its job.

Cc: 
Signed-off-by: Jan Kara 
Signed-off-by: Andrew Morton 
Signed-off-by: Mingming Cao 
Signed-off-by: "Theodore Ts'o"