Re: Accidentally created systemd units for OSDs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I would expect it to be:

systemctl disable ceph-osd@${instance}

If you're wanting to disable them all I believe you can even use wildcards:

systemctl disable ceph-osd@\*
--
Adam

On 8/16/24 2:24 PM, Dan O'Brien wrote:
This email originated from outside of K-State.


I am 100% using cephadm and containers and plan to continue to do so.

Our original setup was all spinners, but after going to Ceph Days NYC, I pushed for SSDs to use for the WAL/RocksDb and I'm in the process of migrating the WAL/RocksDb. In general, it's been fairly straightforward -- IF YOU FOLLOW THE DIRECTIONS EXACTLY. From what I can tell (and someone please correct me if I'm wrong), it appears that I've just introduced a bit of cruft into systemd that duplicates the configuration of the container OSD. If I can get rid of that bit of bellybutton-lint, I think I'm OK without rebuilding the OSD. (At least until I screw it up again on one of the remaining OSDs I need to migrate).

Anyone know how to get rid of an instance of a templated systemd unit? PLEEEEEEEEEEZE?
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux