Hi,
P.S. Oh yeah, it should be noted that freezing at the filesystem
layer does *not* guarantee that changes to the block device aren't
happening via mmap()'ed files. The LVM needs to freeze writes the
block device level if it wants to guarantee a completely stable
snapshot image. So the
On Wed, 2008-02-13 at 17:26 +0100, Valerie Clement wrote:
Modify the block allocation algorithm for the last group
From: Valerie Clement [EMAIL PROTECTED]
When a directory inode is allocated in the last group and the last group
contains less than s_blocks_per_group blocks, the initial
Fix kernel BUG at fs/ext4/mballoc.c:910!
From: Valerie Clement [EMAIL PROTECTED]
With the flex_bg feature enabled, a large file creation oopses the
kernel.
The BUG_ON is:
BUG_ON(len = EXT4_BLOCKS_PER_GROUP(sb));
As the allocation of the bitmaps and the inode table can be done
outside
On Feb 13, 2008 18:19 +0100, Valerie Clement wrote:
From: Valerie Clement [EMAIL PROTECTED]
With the flex_bg feature enabled, a large file creation oopses the
kernel.
The BUG_ON is:
BUG_ON(len = EXT4_BLOCKS_PER_GROUP(sb));
As the allocation of the bitmaps and the inode table can be
The patch titled
ext4: le*_add_cpu conversion
has been added to the -mm tree. Its filename is
ext4-le_add_cpu-conversion.patch
Before you just go and hit reply, please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the
The patch titled
jbd: sparse warnings in revoke.c, journal.c
has been added to the -mm tree. Its filename is
jbd-sparse-warnings-in-revokec-journalc.patch
Before you just go and hit reply, please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as
New bitmap and inode table allocation for FLEX_BG
From: Jose R. Santos [EMAIL PROTECTED]
Change the way we allocate bitmaps and inode tables if the FLEX_BG
feature is used at mke2fs time. It places calculates a new offset for
bitmaps and inode table base on the number of groups that the user
