"Vacuum Full Analyze" taking so long

I have an 8.02 postgresql database with about 180 GB in size, running on
2.6 RedHat kernel with 32 GB of RAM and 2 CPUs. I'm running the vacuum
full analyze command, and has been running for at least two consecutive
days with no other processes running (it's an offline loading server). I
tweaked the maintenanace_mem to its max (2 GB) with work_mem of 8M. I
have no issues with my checkpoints. I can still I/O activities against
the physical files of the "property" table and its two indexes (primary
key and r index). The property files are about 128GB and indexes are
about 15 GB. I have run the same maintenance job on a different box
(staging) with identical hardware config (except with 64 GB instead of
32) and took less than 12 hours.   Any clue or tip is really
appreciated.

Also read a comment by Tom Lane, that terminating the process should be
crash-safe if I had to.

Thanks,


--
 Husam

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

**********************************************************************
This message contains confidential information intended only for the
use of the addressee(s) named above and may contain information that
is legally privileged.  If you are not the addressee, or the person
responsible for delivering it to the addressee, you are hereby
notified that reading, disseminating, distributing or copying this
message is strictly prohibited.  If you have received this message by
mistake, please immediately notify us by replying to the message and
delete the original message immediately thereafter.

Thank you.                                       FADLD Tag
**********************************************************************