From: Mark Nelson <mark.nelson@inktank.com>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org, james.page@ubuntu.com, gcs@debian.hu
Subject: Re: deb/rpm package purge
Date: Tue, 19 Mar 2013 15:05:02 -0500 [thread overview]
Message-ID: <5148C4EE.5090205@inktank.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1303191246330.4850@cobra.newdream.net>
On 03/19/2013 02:48 PM, Sage Weil wrote:
> Should the package purge remove /var/lib/ceph/* (potential mon data, osd
> data) and/or /var/log/ceph/* (logs)? Right now it does, but mysql, for
> example, leaves /var/lib/mysql where it is (not sure about logs).
I'm definitely for leaving mon/osd data in place. Those files are
created at cluster creation time, not when the packages are installed.
They may have been created by a totally different installation of Ceph
than the packaged version.
What's worse is that you can't get the files back simply by reinstalling
the package. With the way things currently are, a package purge will
effectively permanently destroy your cluster. Purge should get rid of
configuration files, but I don't think it should destroy user data which
is what it effectively is doing now.
>
> sage
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-03-19 20:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 19:48 deb/rpm package purge Sage Weil
2013-03-19 19:59 ` Greg Farnum
2013-03-19 20:05 ` Mark Nelson [this message]
2013-03-19 20:46 ` Dan Mick
2013-03-19 20:51 ` Sage Weil
2013-03-19 22:27 ` Laszlo Boszormenyi (GCS)
2013-03-19 22:29 ` Sage Weil
2013-03-19 22:51 ` Laszlo Boszormenyi (GCS)
2013-03-19 22:59 ` Sage Weil
2013-03-20 6:29 ` Laszlo Boszormenyi (GCS)
2013-03-20 12:48 ` Sage Weil
2013-03-20 14:48 ` Mark Nelson
2013-03-20 17:27 ` James Page
2013-03-20 23:23 ` Laszlo Boszormenyi (GCS)
2013-03-21 1:08 ` Dan Mick
2013-03-19 23:01 ` Mark Nelson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5148C4EE.5090205@inktank.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gcs@debian.hu \
--cc=james.page@ubuntu.com \
--cc=sage@inktank.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.