Hi folks,
New version of the Flex_BG ialloc allocation patch.
Changes from the last version:
- Size of the FLEX_BG in now written to the super block at mke2fs time
instead of calculating at mount time (testing patch for e2fsprog's
next branch attached).
- Rename a lots of the confusing "met
On Wed, 2007-12-05 at 16:01 -0800, Andrew Morton wrote:
> No, I think print_hex_dump() is too low-level to be doing allocations.
> For example, one could easily choose to call print_hex_dump() at oops time,
> and then what happens if we oops in kmalloc() (as we often do...)?
>
> You could trim li
On Dec 06, 2007 15:21 +0100, Jan Kara wrote:
> attached is a test script which verifies that 64KB blocksize works in the
> modified code paths. It creates a filesystem with 64KB blocksize and
> excercises e2image, debugfs (and thus libext2fs) and e2fsck on it. You only
> need to modify paths to
Hi,
attached is a test script which verifies that 64KB blocksize works in the
modified code paths. It creates a filesystem with 64KB blocksize and
excercises e2image, debugfs (and thus libext2fs) and e2fsck on it. You only
need to modify paths to e2fsprogs in the first few lines of the script.
Hi,
attached patch modifies mke2fs to always create lost+found with at least
two directory blocks. I think this could make sence not only for testing
but as a sanity check that 64KB support works for general e2fsprogs if
someone decides to use it...
Hi,
attached is a new version of support for 64KB blocksize in e2fsprogs. The
patch went through testing by a script I'll send in the following email so
now the modifications should be correct. Ted, can you have a look at it
when you have time? Thanks.
