influx_inspect verify aborts when tsm file is 0 bytes and doesn't print the culprit file

Influxdb is running after power outage, however I can't verify which files are affected, doing a
`influx_inspect verify -dir /var/lib/influxdb/`
leads to this error message
```
Broken Blocks: 0 / 0, in 0.000149687s
verify: init: error reading magic number of file: EOF
```
Influxdb is running, but I'd like to see which files are affected.

Start with the `influx_inspect verify` command and reproduce the failure using a zero-byte TSM file in the specified directory. Done means verification does not abort without identifying the affected file, while preserving useful error output.

Written by the indexing model from the issue text.