error: failed to call blockstore.GetSize for shard reader closed"}

### Checklist

- [X] This is **not** a question or a support request. If you have any boost related questions, please ask in the [discussion forum](https://github.com/filecoin-project/boost/discussions).
- [X] This is **not** a new feature request. If it is, please file a [feature request](https://github.com/filecoin-project/boost/issues/new?assignees=&labels=need%2Ftriage%2Ckind%2Ffeature&template=feature_request.yml) instead.
- [X] This is **not** an enhancement request. If it is, please file a [improvement suggestion](https://github.com/filecoin-project/boost/issues/new?assignees=&labels=need%2Ftriage%2Ckind%2Fenhancement&template=enhancement.yml) instead.
- [X] I **have** searched on the [issue tracker](https://github.com/filecoin-project/boost/issues) and the [discussion forum](https://github.com/filecoin-project/boost/discussions), and there is no existing related issue or discussion.
- [X] I am running the [`Latest release`](https://github.com/filecoin-project/boost/releases), or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
- [X] I did not make any code changes to boost.

### Boost component

- [X] boost daemon - storage providers
- [ ] boost client
- [ ] boost UI
- [X] boost data-transfer
- [X] boost index-provider
- [ ] Other

### Boost Version

```text
boostd version 1.7.2+git.4214dd7.dirty
```

### Describe the Bug

Seeing a lot of these errors every day. dagstore has the piece and shard is available.

`{"level":"error","ts":"2023-05-05T04:46:39.350-0700","logger":"engine","caller":"decision/blockstoremanager.go:99","msg":"blockstore.GetSize(bafk2bzacea37buvihtydk5pnnluhfzcgnxsmqqj5j4hzyfuhwfirnibojfk42) error: failed to call blockstore.GetSize for shard baga6ea4seaqanhzuxyavi6ovzegqtmsg7c3k6gev3g74sxe3qz6jg3ipazb56bi: reader closed"}`

```
scaseye@homemate-server01:~$ grep "2023-05-03" logs/booster-bitswap.log |grep "failed to call blockstore.GetSize" | wc -l
191
scaseye@homemate-server01:~$ grep "2023-05-02" logs/booster-bitswap.log |grep "failed to call blockstore.GetSize" | wc -l
641
scaseye@homemate-server01:~$ grep "2023-05-01" logs/booster-bitswap.log |grep "failed to call blockstore.GetSize" | wc -l
426
scaseye@homemate-server01:~$ grep "2023-05-04" logs/booster-bitswap.log |grep "failed to call blockstore.GetSize" | wc -l
954
```

$ boostd dagstore lookup-piece-cid bafk2bzacea37buvihtydk5pnnluhfzcgnxsmqqj5j4hzyfuhwfirnibojfk42
Given CID was found in the following pieces: [baga6ea4seaqanhzuxyavi6ovzegqtmsg7c3k6gev3g74sxe3qz6jg3ipazb56bi]

$ boostd dagstore list-shards |grep baga6ea4seaqanhzuxyavi6ovzegqtmsg7c3k6gev3g74sxe3qz6jg3ipazb56bi
baga6ea4seaqanhzuxyavi6ovzegqtmsg7c3k6gev3g74sxe3qz6jg3ipazb56bi Available

### Logging Information

```text
https://filecoinproject.slack.com/archives/C03CKDLEWG1/p1683306478191079
```

### Repo Steps

1. Run '...'
2. Do '...'
3. See error '...'
...
https://filecoinproject.slack.com/archives/C03CKDLEWG1/p1683306478191079

Start with decision/blockstoremanager.go at the reported line and inspect the blockstore.GetSize path for the shard reader-closed error. Use the supplied boostd dagstore lookup-piece-cid and dagstore list-shards commands to compare the reported piece and shard state; the issue does not specify a reproduction or acceptance condition, so confirm the intended fix with maintainers.

Written by the indexing model from the issue text.