Sorry for the spam, but I need to add this disclaimer:
Although it is documented as safe to disable volatile write cache on a disk in use, I
would probably not do it. The required cache flush might be erroneous in the firmware.
Therefore, the method I use will not necessarily apply to OSD set-ups with WAL/DB
partitions, multiple OSDs per disk and other set-ups where several daemons share the same
drive. Here, more logic seems warranted. This also means that OSD daemons can probably not
just do it without checking if a drive is currently in use or not.
Best regards,
=================
Frank Schilder
AIT Risø Campus
Bygning 109, rum S14
________________________________________
From: Frank Schilder <frans(a)dtu.dk>
Sent: 24 June 2020 18:00:19
To: Marc Roos; paul.emmerich
Cc: bknecht; ceph-users; s.priebe
Subject: [ceph-users] Re: High ceph_osd_commit_latency_ms on Toshiba MG07ACA14TE HDDs
I use the stable ceph/daemon containers and introduced my own startup script for the
container entrypoint. On the action "disk activate", it does a smartctl on the
device argument before executing entrypoint.sh.
Best regards,
=================
Frank Schilder
AIT Risø Campus
Bygning 109, rum S14
________________________________________
From: Marc Roos <M.Roos(a)f1-outsourcing.eu>
Sent: 24 June 2020 17:55:35
To: Frank Schilder; paul.emmerich
Cc: bknecht; ceph-users; s.priebe
Subject: RE: [ceph-users] Re: High ceph_osd_commit_latency_ms on Toshiba MG07ACA14TE HDDs
I run the corresponding smartctl command on every
drive just before
OSD daemon start.
How/where did you do this?
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io