In the Debian world, purge does both a removal of the package and a clean up the files so might be good to keep semantic consistency here?
On Tue, Nov 5, 2013 at 1:11 AM, Sage Weil <sage@xxxxxxxxxxxx> wrote:
Purgedata is only meant to be run *after* the package is uninstalled. We should make it do a check to enforce that. Otherwise we run into these problems...
Mark Kirkwood <mark.kirkwood@xxxxxxxxxxxxxxx> wrote:On 05/11/13 06:37, Alfredo Deza wrote:On Mon, Nov 4, 2013 at 12:25 PM, Gruher, Joseph R
<joseph.r.gruher@xxxxxxxxx> wrote:Could these problems be caused by running a purgedata but not a purge?
It could be, I am not clear on what the expectation was for just doing
purgedata without a purge.Purgedata removes /etc/ceph but without the purge ceph is still installed,
then ceph-deploy install detects ceph as already installed and does not
(re)create /etc/ceph?
ceph-deploy will not create directories for you, that is left to the
ceph install process, and just to be clear, the
latest ceph-deploy version (1.3) does not remote /etc/ceph, just the contents.
Yeah, however purgedata is removing /var/lib/ceph, which means after
running purgedata you need to either run purge then install or manually
recreate the various working directories under /var/lib/ceph before
attempting any mon. mds or osd creation.
Maybe purgedata should actually leave those top level dirs under
/var/lib/ceph?
regards
Markceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
