The most likely cause of this is not that the node is not getting any data, but that the node has not yet flushed to disk. The write path of Cassandra goes first to a memtable and on-disk commitlog. As long as that memtable is not flushed you won't see the amount of disk space used go up. Try running
nodetool flush
on 204.13.85.2 to force the memtable to disk and see if the number goes up. This would be naturally triggered if you inserted more data.