0 MB swap 1024 MB error

[smokenbiskits]

This is a problem I ran into. I was testing different sizes of swap/fs to see if there's a difference. When I tried 0mb swap/1024mb system I wasn't able to go to ext 3 or repair. Any help on ADB use of these commands or information on why would be nice. Also this is my first video so any constructive criticism would be nice.

I wasn't able to embed, so here's a link

http://youtu.be/tQcERJ3W8Yg?hd=1

 

[obijohn]

Did you create 3 partitions (fat, ext3, swap) or 2? It may just be a partitioning issue.

That said, on the V there is absolutely no need for swap. There's a difference between "internal memory", which is the data partition and used to install apps and store data, and "available memory" (or RAM). "Internal memory" will gradually go down as you install apps. RAM is typically starts out at around 300MB available upon boot. As apps run and use RAM, that number may drop to around 200MB, but I've never seen it go below 185MB, and I use a lot of apps.

Swap was developed as an option when the G1 was the only Android phone on the Market, and it had very little available RAM. There's simply no need for it on the V, and it can even slow down the phone.

 

[smokenbiskits]

check out the video, but I specified 2 through thunder with the third being default all the other space...I'm doing benchmarks right now and so far there is a good argument for swap....I'll post it all when I'm done

 

[bigsupersquid]

@op, what kernel are you using? the 2.6.32.33- aospcmod does not appear to support swapfs, nor zefie's xionia kernel.

 

[smokenbiskits]

that is the kernel I'm using

 

[bigsupersquid]

so I guess I don't understand how you're using swap.
the swapon shell command returns unsupported, and at least zefie's kernel config file shows swapfs support is not built into the kernel; I've read that the aosp kernel is using zefie's tweaks.
are you using an app or something?
edit: you mention thunder in a post, and your video shows a pc desktop connected (through ADB?) and another window, which is what?.
have you tried running e2fsck?

adb shell
e2fsck /dev/block/mmcblk0p2
exit