All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brett Russ <icycle@charter.net>
To: Valdis.Kletnieks@vt.edu
Cc: Nikita Danilov <Nikita@namesys.com>,
	Reiserfs-List <reiserfs-list@namesys.com>
Subject: Re: % of filesystem using tails/tail unpacking (shred related)
Date: Mon, 28 Oct 2002 17:38:57 -0500	[thread overview]
Message-ID: <3DBDBC81.4040703@charter.net> (raw)
In-Reply-To: 200210282120.g9SLKvgn005200@turing-police.cc.vt.edu

Valdis.Kletnieks@vt.edu wrote:
> On Mon, 28 Oct 2002 12:55:20 +0300, Nikita Danilov said:
> 
>>Brett Russ writes:
> 
> 
>> > 1) as mentioned first, an impact study should be done to determine if
>> > unpacking will overflow the available space on the device
>>
>>Why cannot you do unpacking just before shredding particular file?
> 
> 
> Unpacking before shredding has a subtle hole in it - since you will unpack
> into *different* disk blocks and then shred *those* blocks, you will be
> leaving unshredded data in the blocks the file occupied before unpacking.

Exactly, that was item #3 on my list.  So given what has been said thus 
far, the following seems to be true:

a) shred will work reliably on all new files created on a filesystem 
mounted with tail packing disabled

b) to deal with filesystems already tail packed, shredding knowledge 
would need to be added to the unpack ioctl BUT there is no way to 
determine where else the tails have lived on disk prior to any rebalancing.

Which leads to:

c) there is no reliable way to shred anything that has been tail packed.

Please affirm or correct my conclusions, and thank you all for your help 
thus far.

-Brett


  reply	other threads:[~2002-10-28 22:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 21:46 % of filesystem using tails/tail unpacking (shred related) Brett Russ
2002-10-28  9:55 ` Nikita Danilov
2002-10-28 21:20   ` Valdis.Kletnieks
2002-10-28 22:38     ` Brett Russ [this message]
2002-10-29  6:10       ` Oleg Drokin

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=3DBDBC81.4040703@charter.net \
    --to=icycle@charter.net \
    --cc=Nikita@namesys.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=reiserfs-list@namesys.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.