head 1.1; access; symbols netbsd-10-0-RELEASE:1.1 netbsd-10-0-RC6:1.1 netbsd-10-0-RC5:1.1 netbsd-10-0-RC4:1.1 netbsd-10-0-RC3:1.1 netbsd-10-0-RC2:1.1 netbsd-10-0-RC1:1.1 netbsd-10:1.1.0.14 netbsd-10-base:1.1 netbsd-9-3-RELEASE:1.1 cjep_sun2x-base1:1.1 cjep_sun2x:1.1.0.12 cjep_sun2x-base:1.1 cjep_staticlib_x-base1:1.1 netbsd-9-2-RELEASE:1.1 cjep_staticlib_x:1.1.0.10 cjep_staticlib_x-base:1.1 netbsd-9-1-RELEASE:1.1 phil-wifi-20200421:1.1 phil-wifi-20200411:1.1 is-mlppp:1.1.0.8 is-mlppp-base:1.1 phil-wifi-20200406:1.1 netbsd-9-0-RELEASE:1.1 netbsd-9-0-RC2:1.1 netbsd-9-0-RC1:1.1 phil-wifi-20191119:1.1 netbsd-9:1.1.0.6 netbsd-9-base:1.1 phil-wifi:1.1.0.4 phil-wifi-20190609:1.1 pgoyette-compat-merge-20190127:1.1.2.2 pgoyette-compat-20190127:1.1 pgoyette-compat-20190118:1.1 pgoyette-compat:1.1.0.2 pgoyette-compat-1226:1.1; locks; strict; comment @# @; 1.1 date 2018.12.07.21.28.03; author jdolecek; state Exp; branches 1.1.2.1 1.1.4.1; next ; commitid aTzOC80bOfwBEU2B; 1.1.2.1 date 2018.12.07.21.28.03; author pgoyette; state dead; branches; next 1.1.2.2; commitid xUhK8IAeBM1azj5B; 1.1.2.2 date 2018.12.26.14.01.13; author pgoyette; state Exp; branches; next ; commitid xUhK8IAeBM1azj5B; 1.1.4.1 date 2018.12.07.21.28.03; author christos; state dead; branches; next 1.1.4.2; commitid jtc8rnCzWiEEHGqB; 1.1.4.2 date 2019.06.10.21.42.38; author christos; state Exp; branches; next ; commitid jtc8rnCzWiEEHGqB; desc @@ 1.1 log @save some notes from my two years old hacking on ext3/ext4 support with our ext2fs @ text @newfs_ext2fs support for EXTRA_ISIZE - not yet bunch of bin ext2 bugs - fsck_ext2fs et.al. 64bit support meta data support - maybe only affects dirs and raises limit on max.filesystem? fix ext4.wiki - h_reserved[2] should actually be h_reserved[3] according to ext4 code xattr - dont forget refcount handling , with hash map (same as linux) - use roundup2() instead of custom macros EXTENTS: check if the inode_ext extents cache is actually used optimalization - on sync, only overwrite changed cgs? adv for bigger filesystems remove dup e2fs_mnton from m_fs maybe return limit to 32000 links for !DIR_NLINK fs (cross-check what Linux ext4 code) QUOTA support ? INODE_DATA support? (even linux is dev only) @ 1.1.4.1 log @file TODO.ext2fs was added on branch phil-wifi on 2019-06-10 21:42:38 +0000 @ text @d1 27 @ 1.1.4.2 log @Sync with HEAD @ text @a0 27 newfs_ext2fs support for EXTRA_ISIZE - not yet bunch of bin ext2 bugs - fsck_ext2fs et.al. 64bit support meta data support - maybe only affects dirs and raises limit on max.filesystem? fix ext4.wiki - h_reserved[2] should actually be h_reserved[3] according to ext4 code xattr - dont forget refcount handling , with hash map (same as linux) - use roundup2() instead of custom macros EXTENTS: check if the inode_ext extents cache is actually used optimalization - on sync, only overwrite changed cgs? adv for bigger filesystems remove dup e2fs_mnton from m_fs maybe return limit to 32000 links for !DIR_NLINK fs (cross-check what Linux ext4 code) QUOTA support ? INODE_DATA support? (even linux is dev only) @ 1.1.2.1 log @file TODO.ext2fs was added on branch pgoyette-compat on 2018-12-26 14:01:13 +0000 @ text @d1 27 @ 1.1.2.2 log @Sync with HEAD, resolve a few conflicts @ text @a0 27 newfs_ext2fs support for EXTRA_ISIZE - not yet bunch of bin ext2 bugs - fsck_ext2fs et.al. 64bit support meta data support - maybe only affects dirs and raises limit on max.filesystem? fix ext4.wiki - h_reserved[2] should actually be h_reserved[3] according to ext4 code xattr - dont forget refcount handling , with hash map (same as linux) - use roundup2() instead of custom macros EXTENTS: check if the inode_ext extents cache is actually used optimalization - on sync, only overwrite changed cgs? adv for bigger filesystems remove dup e2fs_mnton from m_fs maybe return limit to 32000 links for !DIR_NLINK fs (cross-check what Linux ext4 code) QUOTA support ? INODE_DATA support? (even linux is dev only) @