What you are seeing is fine. The current libxfs cache with the directory update
code is leaving some blocks referenced,
and the libxfs code is printing out these blocks with outstanding references.
The actual data was written to disk (prior to 2.8.10 it may not have).
> -----Original Message-----
> From: xfs-bounce@xxxxxxxxxxx [mailto:xfs-bounce@xxxxxxxxxxx]
> On Behalf Of Paul Slootman
> Sent: Friday, 11 August 2006 2:42 AM
> To: xfs@xxxxxxxxxxx
> Subject: cache_purge: shake on cache 0x5880a0 left 8 nodes!?
> I had problems due to the well-known endian bug.
> I first ran xfs_repair on it from the standard Debian package,
> version 2.6.20. That gave a lot of output (which can be found at
> http://www.xs4all.nl/~wurtel2/xfs_repair.out.4 ).
> While that was running, I got today's CVS version and built that
> (it reports version 2.8.11). I ran that version against the
> just-repaired filesystem, and got a number of additional errors,
> empty data block 10 in directory inode 1343747104: junking block
> empty data block 11 in directory inode 1343747104: junking block
> empty data block 12 in directory inode 1343747104: junking block
> free block 16777216 entry 10 for directory ino 1343747104 bad
> rebuilding directory inode 1343747104
> This 7 times; additionally, this was mentioned a couple of times:
> cache_purge: shake on cache 0x5880a0 left 8 nodes!?
> In fact, twice before the final "done.".
> The second repair output can be found at
> http://www.xs4all.nl/~wurtel2/xfs_repair.out.4b .
> Should I be worried about that? I tried a search for "shake on cache"
> and found zero hits...
> Additionally, the hash hit rates seem pretty bad. Anything to be
> worried about, and could anything be done about it?
> Paul Slootman (please CC me on responses)