linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 92271] Provide a way to really delete files, please
Date: Thu, 29 Jan 2015 19:49:51 +0000	[thread overview]
Message-ID: <bug-92271-13602-33GMbVggfT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-92271-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=92271

--- Comment #3 from Alexander Holler <holler@ahsoftware.de> ---
It doesn't work for on FLASH based devices which have their own logic (e.g.
SD-cards or SSDs, there "Secure Trim" is needed). 

And just overwriting a file by using open(); write(); close(); likely doesn't
work with ext4 on traditional harddisks (or similiar blockdevices) too.

Also I'm not sure about the last fact, as I'm not really aware of the internal
workings of ext4.

At least I've never read anywhere a statement, that by writing the same amount
of bytes to a file as already there, the fs will for sure overwrite the same
blocks on disk as already occupied/used by the file.

So a special syscall or similiar is needed to instruct the fs to overwrite the
same, already used blocks (even if they are stored only in the metadata because
the file is small enough).

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2015-01-29 19:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 11:47 [Bug 92271] New: Provide a way to really delete files, please bugzilla-daemon
2015-01-29 19:13 ` [Bug 92271] " bugzilla-daemon
2015-01-29 19:30 ` bugzilla-daemon
2015-01-29 19:49 ` bugzilla-daemon [this message]
2015-01-29 20:59 ` bugzilla-daemon
2015-01-29 21:01 ` bugzilla-daemon
2015-01-29 21:20 ` bugzilla-daemon
2015-01-29 21:55 ` bugzilla-daemon
2015-01-29 22:02 ` bugzilla-daemon
2015-01-29 22:11 ` bugzilla-daemon
2015-01-31 17:21 ` bugzilla-daemon
2015-01-31 18:36 ` bugzilla-daemon
2015-01-31 20:56 ` bugzilla-daemon
2015-02-01  1:51 ` bugzilla-daemon
2015-02-01  1:58 ` bugzilla-daemon
2015-02-01 10:14 ` bugzilla-daemon
2015-02-01 10:35 ` bugzilla-daemon
2015-02-01 11:04 ` bugzilla-daemon
2015-02-01 16:33 ` bugzilla-daemon
2015-02-01 17:18 ` bugzilla-daemon
2015-02-02  8:32 ` bugzilla-daemon
2015-02-02 11:13 ` bugzilla-daemon
2015-02-02 17:12 ` bugzilla-daemon
2015-02-03 17:29 ` bugzilla-daemon
2015-02-03 17:44 ` bugzilla-daemon
2015-02-03 17:47 ` bugzilla-daemon
2015-02-03 18:20 ` bugzilla-daemon

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=bug-92271-13602-33GMbVggfT@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).