> Op 19 september 2017 om 10:24 schreef Adrian Saul > <[email protected]>: > > > > I understand what you mean and it's indeed dangerous, but see: > > https://github.com/ceph/ceph/blob/master/systemd/ceph-osd%40.service > > > > Looking at the systemd docs it's difficult though: > > https://www.freedesktop.org/software/systemd/man/systemd.service.ht > > ml > > > > If the OSD crashes due to another bug you do want it to restart. > > > > But for systemd it's not possible to see if the crash was due to a disk I/O- > > error or a bug in the OSD itself or maybe the OOM-killer or something. > > Perhaps using something like RestartPreventExitStatus and defining a specific > exit code for the OSD to exit on when it is exiting due to an IO error. >
That's a very, very good idea! I didn't know that one existed. That would prevent restarts in case of I/O error indeed. Wido > Confidentiality: This email and any attachments are confidential and may be > subject to copyright, legal or some other professional privilege. They are > intended solely for the attention and use of the named addressee(s). They may > only be copied, distributed or disclosed with the consent of the copyright > owner. If you have received this email by mistake or by breach of the > confidentiality clause, please notify the sender immediately by return email > and delete or destroy all copies of the email. Any confidentiality, privilege > or copyright is not waived or lost because this email has been sent to you by > mistake. _______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
