spurious files next to container hashdir don't get cleaned up

[clayg]

I'm looking at something like this

/srv/node1/sdb1/containers
└── 450
    ├── afb # empty suffix
    ├── afc
    │   ├── 7089ab48d955ab0851fc51cc17a34afc # bogus file
    │   └── c8bcccab3ddbfdc34b08e9223f4f5afc # empty hashdir
    └── afd
        └── 7089ab48d955ab0851fc51cc17a34afd
            └── 7089ab48d955ab0851fc51cc17a34afd.db

The empty dirs can get cleaned up with a fix for lp bug #1583719

But the bogus file still remains.

A file where a hashdir should be (or hashdir where a file should be, i.e. lp bug #1621255) are currently understood to be some kinda of filesystem corruption.

We should either delete these bogus files or maybe better quarantine them.

For objects, it slightly worse lp bug #1646502

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/405134

[John Dickinson (notmyname)]

The referenced patch has been merged, so I'll mark this as "fix released". the other referenced bugs are tracked separately.