From: Igor Fedotov <ifedotov@mirantis.com>
To: Gregory Farnum <gfarnum@redhat.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Wiping object content on removal
Date: Tue, 24 Nov 2015 20:04:36 +0300 [thread overview]
Message-ID: <565498A4.2070001@mirantis.com> (raw)
In-Reply-To: <CAJ4mKGYuQ0mPU+BPXOU=_3Tqf+ySLmiUfozi0hNbybJLkkxVRw@mail.gmail.com>
Gregory,
the idea is to wipe object content optionally - when user requests for that.
Thus not every delete operation will suffer from that.
Igor.
On 11/23/2015 8:11 PM, Gregory Farnum wrote:
> On Mon, Nov 23, 2015 at 10:44 AM, Igor Fedotov <ifedotov@mirantis.com> wrote:
>> Hi Gregory,
>>
>> On 23.11.2015 18:52, Gregory Farnum wrote:
>>> On Wed, Nov 18, 2015 at 8:42 AM, Igor Fedotov <ifedotov@mirantis.com>
>>> wrote:
>>>> Hi Cephers.
>>>>
>>>> Does Ceph have an ability to wipe object content during one's removal?
>>>> Surely one can do that manually from the client but I think that's
>>>> ineffective and not 100% secure.
>>>>
>>>> If no - what's about adding such feature to Ceph?
>>>> I can start working on that.
>>> Wipe object content during removal of what? The OSD? Or are you
>>> talking about secure erase of object data instead of unlinking files?
>> I meant secure object removal.
>>
> Yeah, I just don't see this happening. There aren't even exposed
> primitives to do a secure erase on SSDs, are there? Plus turning a
> delete operation into a full data overwrite....yuck.
> -Greg
prev parent reply other threads:[~2015-11-24 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 14:42 Wiping object content on removal Igor Fedotov
2015-11-23 15:52 ` Gregory Farnum
2015-11-23 16:44 ` Igor Fedotov
2015-11-23 16:53 ` Andrey Korolyov
2015-11-24 16:58 ` Igor Fedotov
2015-11-23 17:11 ` Gregory Farnum
2015-11-24 17:04 ` Igor Fedotov [this message]
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=565498A4.2070001@mirantis.com \
--to=ifedotov@mirantis.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gfarnum@redhat.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.