Christop, do you have any links to the bug?
On Fri, Dec 21, 2018 at 11:07 AM Christoph Adomeit <
christoph.adom...@gatworks.de> wrote:
> Hi,
>
> same here but also for pgs in cephfs pools.
>
> As far as I know there is a known bug that under memory pressure some
> reads return zero
> and this
Hi,
same here but also for pgs in cephfs pools.
As far as I know there is a known bug that under memory pressure some reads
return zero
and this will lead to the error message.
I have set nodeep-scrub and i am waiting for 12.2.11.
Thanks
Christoph
On Fri, Dec 21, 2018 at 03:23:21PM +0100,
Hi Frank,
I encounter exactly the same issue with the same disks than yours. Every
day, after a batch of deep scrubbing operation, ther are generally
between 1 and 3 inconsistent pgs, and that, on different OSDs.
It could confirm a problem on these disks, but :
- it concerns only the pgs of
>I will also see a few uncorrected read errors in smartctl.
uncorrected read errors in smartctl is a cause for us to replace the drive.
On Wed, Dec 19, 2018 at 6:48 AM Frank Ritchie wrote:
>
> Hi all,
>
> I have been receiving alerts for:
>
> Possible data damage: 1 pg inconsistent
>
> almost
Hi all,
I have been receiving alerts for:
Possible data damage: 1 pg inconsistent
almost daily for a few weeks now. When I check:
rados list-inconsistent-obj $PG --format=json-pretty
I will always see a read_error. When I run a deep scrub on the PG I will
see:
head candidate had a read error
