mentioning that resolution of moveChunk is still required

Author: Andrew Leung

source/faq/sharding.txt

@@ -351,7 +351,8 @@ view of all chunks. For this situation, the :term:`primary` member of
 the shard will terminate
 itself to prevent data inconsistency. If the config database is
 accessible by the :term:`secondary` members, the shard's data will be
-accessible after an election.
+accessible after an election but the chunk migration failure will need
+to be resolved.
 
 If you encounter this issue, contact the `MongoDB User Group
 <http://groups.google.com/group/mongodb-user>`_ or 10gen support to