[Galaxy S I9000 Android Development] hardcore:
@sztupy:

WARNING! Do NOT use ANY LAGFIX from Universal Lagfix with the DXJPA firmware, or any firmware using the 513 PIT. There seems to be compatibility problems with the ULFK and that combination.

Big problems with the new DXJPA firmware that needs to use the 513 PIT.

People have been trying (on my SpeedMod kernel) to use the Voodoo lagfix (ext4 /data) after installing DXJPA.

The filesystem conversion seems to go fine, but the phone won't boot after that.

I checked the /res/pre-init.log, and it looks like /dbdata (rfs) is not getting mounted:

$ cat /res/pre-init.log
cat /res/pre-init.log
Unmounting filesystems
umount: can't umount /dev/block/stl11: Invalid argument
umount: can't umount /dev/block/stl10: Invalid argument
umount: can't umount /dev/block/mmcblk0p2: Invalid argument
Creating mount points
mkdir: can't create directory '/data': File exists
mkdir: can't create directory '/system': File exists
Checking /system
mkdir: can't create directory '/system': File exists
rm: can't remove '/system/bin/fat.format': No such file or directory
checking filesystem and creating lagfix config
fsck.jfs version 1.1.14, 06-Apr-2009
processing started: 11/20/2010 17.46.28
The current device is: /dev/block/mmcblk0p2

The superblock does not describe a correct jfs file system.

If device /dev/block/mmcblk0p2 is valid and contains a jfs file system,
then both the primary and secondary superblocks are corrupt
and cannot be repaired, and fsck cannot continue.

Otherwise, make sure the entered device /dev/block/mmcblk0p2 is correct.

fsck.jfs version 1.1.14, 06-Apr-2009
processing started: 11/20/2010 17.46.28
The current device is: /dev/block/stl10

The superblock does not describe a correct jfs file system.

If device /dev/block/stl10 is valid and contains a jfs file system,
then both the primary and secondary superblocks are corrupt
and cannot be repaired, and fsck cannot continue.

Otherwise, make sure the entered device /dev/block/stl10 is correct.

fsck.jfs version 1.1.14, 06-Apr-2009
processing started: 11/20/2010 17.46.28
The current device is: /dev/block/stl11

The superblock does not describe a correct jfs file system.

If device /dev/block/stl11 is valid and contains a jfs file system,
then both the primary and secondary superblocks are corrupt
and cannot be repaired, and fsck cannot continue.

Otherwise, make sure the entered device /dev/block/stl11 is correct.

mount: mounting /dev/block/mmcblk0p2 on /data failed: Invalid argument
mount: mounting /dev/block/stl10 on /dbdata failed: Invalid argument
mount: mounting /dev/block/stl11 on /cache failed: Device or resource busy
check for loop files
check for bind mounts
The actual config is:
DATA_FS=ext4
CACHE_FS=rfs
DBDATA_FS=rfs
DATA_LOOP=false
CACHE_LOOP=false
DBDATA_LOOP=false
BIND_DATA_TO_DBDATA=false
Configs are the same, load up the mounts
running filesystem checks
Trying to mount /dev/block/mmcblk0p2 to /res/odata
Run a filesystem check on it
DATA: 2096/122880 files (0.2% non-contiguous), 105465/491520 blocks
mount: mounting /dev/block/stl10 on /dbdata failed: Invalid argument

I think what's happening is that the filesystem conversion process does not correctly create the rfs partition for /dbdata if the 513 PIT is used. For the 513 PIT, the /dbdata partition is smaller.

Any idea how to fix it?