without understanding exactly why people are seeing the no space or dbfull error, I'd just say that the planned hardfork that happened friday was done with very little lead time, especially compared to previous forks. So there are quite a few old clients around and at least 1 or two miners it seems.
Because of that , there are two Sexcoin blockchains being produced.... call them the 6.4.6 chain and the 6.4.4-5 chain. Cryptsy and most pools have upgraded and are running on chain 6.4.6, along with most dedicated nodes we know of.
In theory if you simply startup the new
6.4.6 client it will mark the blocks belonging to the 6.4.4 chain as Orphans and move on with the 6.4.6 chain. In reality it seems that this is not happening. It could be that there is too much of the 6.4.4 chain synced onto the client and it simply won't mark that many blocks, going back that far, as Orphans. I'd have to read into the code to find out.
What seems to be the "fix" is to delete the downloaded blockchain and redownload.
Digdug on sexcoinforum.org has been looking at this issue and built a new bootstrap package. This won't prevent you from having to download a large amount of data, but it will speed things up since it's all in one file and zipped up.
You can get it here:
http://datajumper.com/Sorry for the current mess, but this hardfork was necessary to stop the KGW Timewarp attack that was reported on this thread a page or 2 back.