If you're using an Icinga active check that just looks for
SMART overall-health self-assessment test result: PASSED
then it's not doing much for you. That bivalue status can be shown for a drive
that is decidedly an ex-parrot. Gotta look at specific attributes, which is
thorny since they
- Le 12 Avr 24, à 15:17, Albert Shih albert.s...@obspm.fr a écrit :
> Le 12/04/2024 à 12:56:12+0200, Frédéric Nass a écrit
>>
> Hi,
>
>>
>> Have you check the hardware status of the involved drives other than with
>> smartctl? Like with the manufacturer's tools / WebUI (iDrac / perccli
Le 12/04/2024 à 12:56:12+0200, Frédéric Nass a écrit
>
Hi,
>
> Have you check the hardware status of the involved drives other than with
> smartctl? Like with the manufacturer's tools / WebUI (iDrac / perccli for
> DELL hardware for example).
Yes, all my disk are «under» periodic check with
check your ceph.log on the mons for "stat mismatch" and grep for the PG in
question for potentially more information.
Additionally "rados list-inconsistent-obj {pgid}" will often show which OSD
and objects are implicated for the inconsistency. If the acting set has
changed since the scrub (for
Hello Albert,
Have you check the hardware status of the involved drives other than with
smartctl? Like with the manufacturer's tools / WebUI (iDrac / perccli for DELL
hardware for example).
If these tools don't report any media error (that is bad blocs on disks) then
you might just be facing
Followup. This is what's written in logs when I try to fix one PG:
ceph pg repair 3.60
primary osd log:
2021-06-25 01:07:32.146 7fc006339700 -1 log_channel(cluster) log [ERR] :
repair 3.53 3:cb4336ff:::rbd_data.e2d302dd699130.69b3:6aa5 : is
an unexpected clone
2021-06-25 01:07:32.146
> all osd hosts that are part of this osd and there's no smart or dmesg
> > errors.
> >
> > Rich
> >
> > --
> > >
> > > Date: Sun, 17 Jan 2021 14:00:01 +0330
> > > From: Seena Fallah
> > > Subject: [
t; Usually these are caused by read errors on the disks, but I've checked
> all osd hosts that are part of this osd and there's no smart or dmesg
> errors.
>
> Rich
>
> ----------
> >
> > Date: Sun, 17 Jan 2021 14:00:01 +0330
> > From: Seena
gt; {
> "epoch": 183807,
> "inconsistents": []
> }
>
> Usually these are caused by read errors on the disks, but I've checked
> all osd hosts that are part of this osd and there's no smart or dmesg
> errors.
>
> Rich
>
> ---
ll osd hosts that are part of this osd and there's no smart or dmesg
errors.
Rich
--
>
> Date: Sun, 17 Jan 2021 14:00:01 +0330
> From: Seena Fallah
> Subject: [ceph-users] Re: PG inconsistent with empty inconsistent
>objects
> To:
t;: 183807,
"inconsistents": []
}
Usually these are caused by read errors on the disks, but I've checked
all osd hosts that are part of this osd and there's no smart or dmesg
errors.
Rich
--
>
> Date: Sun, 17 Jan 2021 14:00:01 +0330
> From: Seena Fallah
&
It's for a long time ago and I don't have the `ceph health detail` output!
On Sat, Jan 16, 2021 at 9:42 PM Alexander E. Patrakov
wrote:
> For a start, please post the "ceph health detail" output.
>
> сб, 19 дек. 2020 г. в 23:48, Seena Fallah :
> >
> > Hi,
> >
> > I'm facing something strange!
For a start, please post the "ceph health detail" output.
сб, 19 дек. 2020 г. в 23:48, Seena Fallah :
>
> Hi,
>
> I'm facing something strange! One of the PGs in my pool got inconsistent
> and when I run `rados list-inconsistent-obj $PG_ID --format=json-pretty`
> the `inconsistents` key was
All of my daemons are 14.2.24
On Sat, Jan 16, 2021 at 2:39 AM wrote:
> Hello Seena,
>
> Which Version of ceph you are using?
>
> IIRC there Was a bug in an older luminous which caused an empty list...
>
> HTH
> Mehmet
>
> Am 19. Dezember 2020 19:47:10 MEZ schrieb Seena Fallah <
>
Hello Seena,
Which Version of ceph you are using?
IIRC there Was a bug in an older luminous which caused an empty list...
HTH
Mehmet
Am 19. Dezember 2020 19:47:10 MEZ schrieb Seena Fallah :
>Hi,
>
>I'm facing something strange! One of the PGs in my pool got
>inconsistent
>and when I run `rados
15 matches
Mail list logo
