> > Well, from the source it is not obvious at all. Is it this cryptic > "rgdtsz" stuff? Can it have a better name? >
reserved group descriptor table size > > Why should I hack vanilla mke2fs? > For both to play the same game. BB mke2fs right now doesn't reserve group descriptors, thus wrong assumptions on free blocks and so on. Just temporarily return 0 for reserved blocks to make sure other things are well. > This last patch does not seem to improve things. Actually, this change: > > - uint32_t ninodes = nblocks_full / (blocksize >= 4096 ? > 1 : 4096 / blocksize); > + //uint32_t ninodes = nblocks_full / (blocksize >= 4096 > ? 1 : 4096 / blocksize); > + uint32_t ninodes = ((uint64_t) nblocks_full * > blocksize) / bytes_per_inode; > > breaks 68 kbyte images. This means mke2fs is even more cryptic. > Other differences did not go away either: > reserved blocks again. Ah, another vanilla feature is to have "/lost+found" occupy by default 24 512-byte blocks! Had to cope with that. Attached patch mimics that behavior. -- Vladimir
test.patch
Description: Binary data
_______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
