You
really should have ran fsck on a Linux machine, it probably wasn't unmounted properly the last time you used it.
Running OpenBSD's fsck_ext2 implementation, especially on a ext3 file system.. was really the worst thing you could have done, obviously fsck meddles with critical filesystem metadata and you had no idea how it would react to it.
The files may be there, but if the metadata was corrupted then it'll be difficult to find them.. if the "inodes" for a ext3 filesystem are removed (..unlinked) then there is nothing pointing to the physical blocks that make up the file, it's practically impossible to recover the files.
Some recovery programs can scan media for known filetype signatures, filenames would be lost.. as would permissions.. file sizes.. basically you messed up big time.
If you want to hold onto hope of recovery, unmount the drive and don't copy anything to it.. otherwise you risk overwriting the blocks they reside in (..some may have already been by fsck).
Here is some guide, for possibly recovering some of it.. but.. it's probably not going to be easy.
http://www.xs4all.nl/~carlo17/howto/undelete_ext3.html