Ext4 Developer Interlock Call: 05/07/2007 Meeting Minutes
Attendees: Mingming Cao, Dave Kleikamp, Ted Ts'o, Aneesh Veetil, Takashi
Sato, Jose Santos, Avantika Mathur,
Minutes can be accessed at:
http://ext4.wiki.kernel.org/index.php/Ext4_Developer%27s_Conference_Call
Discussed pushing ext4 patches upstream.
- Preallocation Patches: These patches are almost ready to push, once we
have consensus from all architecture maintainers on the format of the
system call. Mingming will help with this.
- Nanosecond Timestamps: Ted will take a closer look at this patch
before pushing
- It was proposed to push everything in the ext4 git tree up until the
unstable patches. Before pushing these patches, we must run tests on
the patches and use the check-patches scripts to perform sanity checking.
e2fsprogs:
- Ted recently posted e2fsprogs-1.39-tyt3; which includes patches
supporting extents. This is a work in progress.
- Jose used the patches to e2fsprogs sent by Valerie Clement to create
large filesystems (with >32-bit block numbers)
-- Ted suggested that these patches be added to e2fsprogs-tyt3, with
a flag set when in use, indicating that no shared libraries should be used.
- Ted is planning to discontinue use of Mercurial for e2fsprogs, and
switch entirely to git. By using git, we can have a stable and
development branch for e2fsprogs. This will also reduce the work Ted
does to create a patch series.
Migration:
- Aneesh looked at the online defragmentation code, and feels it may not
be usable for migration because it is solely extents based. Mingming
pointed out that the new defrag patches also have support for indirect
mapped blocks, Aneesh will look into these new patches.
- Ted suggested doing the migration through two ioctls, the first
migrating the inode online via ioctl, and the second using the
online-defrag ioctl.
Metablock Groups:
- Mingming mentioned that in the metablock group feature, the inode
metadata is not moved with the rest of the metadata. Ted will check
this, as he thought this had been implemented.
- Online resize does not use metablock groups, and is currently limited
to 2TB.
- Also need to remove sanity checks in the mount code
- Once these issues are fixed, the metablock group feature can be turned
on by default for ext4 filesysytems
- The extents option will be turned on by default for all ext4
filesystems with the extents feature enabled.
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
