We recently sharded a replica set and missed a process update which allowed that process to bypass the mongos and continue writing GridFS documents directly to the original replica set. The mongos seems to be aware of the fs.files document but cant find the fs.chunks related to that document. The fs.chunks can be found by going directly to the original mongod. Is there an easy way to tap mongos on the shoulder and say "hey, look over there"?
