Gluster users - Nov 2016 - Conflicting info on whether replicated bricks both online

On the one hand:

  # gluster volume heal foretee info healed
  Gathering list of healed entries on volume foretee has been unsuccessful on
bricks that are down. Please check if all brick processes are running.
  root at bu-4t-a:/mnt/gluster# gluster volume status foretee
  Status of volume: foretee
  Gluster process                             TCP Port  RDMA Port  Online  Pid
  ------------------------------------------------------------------------------
  Brick bu-4t-a:/mnt/gluster                  49153     0          Y       9807 
  Brick bu-4t-b:/mnt/gluster                  49152     0          Y       24638
  Self-heal Daemon on localhost               N/A       N/A        Y       2743 
  Self-heal Daemon on bu-4t-b                 N/A       N/A        Y       12819
   
  Task Status of Volume foretee
  ------------------------------------------------------------------------------
  There are no active volume tasks

On the other:

  # gluster volume heal foretee info healed
  Gathering list of healed entries on volume foretee has been unsuccessful on
bricks that are down. Please check if all brick processes are running.

And:

  # gluster volume heal foretee info
  ...
  Status: Connected
  Number of entries: 3141

Both systems have their bricks in /mnt/gluster, and the volume then mounted
in /backups. I can write or delete a file in /backups on either system, and
it appears in both /backups on the other, and in /mnt/gluster on both. 

So Gluster is working. There have only ever been the two bricks. But there
are 3141 entries that won't heal, and a suggestion that one of the bricks is
offline -- when they're both plainly there.

This is with glusterfs 3.8.5 on Ubuntu 16.04.1.

What's my next move?

Thanks, 
Whit