Overview

When working on the DXi platform, you may encounter two similar types of reference count issues. As discussed below, the first one is not an issue and can safely be ignored. But the second one indicates a real problem that needs to be resolved quickly. 

By differentiating between the two types of "Blob" reference count issues, you can save a lot of time and effort.

First Issue: "Blob" Reference Counts Not Trusted

The first type of reference count issue involves “Blob” reference counts not being trusted. You’ll see this in the /var/log/messages file.  It sounds serious but actually is not a problem since the blockpool doesn’t really use the blob reference counts for anything. Messages like the one below can be safely ignored.

Dec  3 13:15:15 BERDXI Blockpool[27849]: W: BLOB reference counts not trusted during BLOB index rebuild. Giving all BLOBs tenure.

Second Issue: "Blocklet" Reference Count in Doubt

The second type of reference count issue is when the “blocklet” reference count is in doubt. You may see this during a verify, in the messages file, in the BPQuickreport, or as a RAS ticket. The blocklet reference counts are critical to the proper operation of the blockpool. When there is any doubt, space reclamation is halted to prevent accidental deletion of good blocklets. When this occurs, you'll see a message like this:  

Apr 30 20:00:13 2013 66 UNKNOWN 66 UNKNOWN UNKNOWN 1112053562 90 Blockpool blocklet reference count in doubt.  Ticket creation time: 04/30 20:00:13 MDT

To correct this, you need to run a blocklet reference count verify. For further informaiton, see this  Qwiki page:

Space Reclamation: BPGC Will Not Reclaim If Reference Count Is in Doubt