[Galaxy 3 Android Development] z3c0:
So the following just happened:

I was still on 2.2.2 OC when my device started behaving weirdly, huge number of Apps FC'ing upon loading Android.

Apparently my /data (ext4 on stl7) partition thought it had "No space left on device", even though df showed only 72% being in use (53.9M free) and fsck.ext4 reported everything being ok.

Here's a bit of adb shell history of what I tested:

/ # mount
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
/dev/block/stl7 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=20,barrier=0,data=ordered,noauto_da_alloc)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
none on /acct type cgroup (rw,relatime,cpuacct)
nodev on /tmp type tmpfs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl6 on /system type ext4 (ro,nodev,noatime,nodiratime,commit=20,barrier=1,data=ordered)
/dev/block/stl8 on /cache type rfs (rw,nosuid,nodev,noatime,nodiratime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437)
/dev/block/stl4 on /efs type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437)
/dev/block/mmcblk0p1 on /mnt/sdcard type vfat (rw,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p2 on /sd-ext type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)

/ # df -h /data
Filesystem Size Used Available Use% Mounted on
/dev/block/stl7 192.4M 138.5M 53.9M 72% /data

/ # touch /data/testfile
touch: /data/testfile: No space left on device

/ # umount /dev/block/stl7

/ # fsck.ext4 /dev/block/stl7
e2fsck 1.41.12 (17-May-2010)
/dev/block/stl7: clean, 12512/12512 files, 36240/50048 blocks

/ # fsck.ext4 -f /dev/block/stl7
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/stl7: 12512/12512 files (3.2% non-contiguous), 36240/50048 blocks

/ # mount -o rw,nosuid,nodev,noatime,nodiratime,commit=20,barrier=0,data=ordered,noauto_da_alloc -t ext4 /dev/block/stl7 /data

/ # touch /data/data/testest
touch: /data/data/testest: No space left on device

Reading from /data was not a problem. At one time after reboot, all of a sudden /data could be written again (wrote 2MB from /dev/urandom to a testfile, then deleted it), only to fall back to "No space left on device" after testing some Apps.

So I thought why not try G3Mod 2.3, perhaps it was some flaky ext4 module that might have been fixed. I updated via .zip, which was done succesfully according to CWM.

But now my device doesn't boot beyond the G3Mod logo (after the progressbar going to 100%) and adb shell doesn't find the device.

Btw, after the 2.3 flash I chose "reboot recovery" instead of normal reboot. Might this be related in some way?

I could try to flash something via Odin but I thought I'd report what happened up until now.

Luckily I did a backup of /data upon first fishy occurences so I could flash / wipe everything I want now without regret. Suggestions?