All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brett Russ" <icycle@charter.net>
To: Reiserfs-List <reiserfs-list@namesys.com>
Subject: % of filesystem using tails/tail unpacking (shred related)
Date: Fri, 25 Oct 2002 17:46:14 -0400	[thread overview]
Message-ID: <HDEFILEPHCPLCAGPLCEMKEMFDFAA.icycle@charter.net> (raw)

Is there a way to analyze an existing ReiserFS and find out how many of the
blocks are tail packed as opposed to full/partially full from the same file?
This could lead to an impact study of converting it to an unpacked state.

From the information I have received so far, the only way shredding can
reliably work on Reiser, tail packing and data journaling need to be
disabled.  However, existing filesystems using tail packing can not be
simply unpacked to separate blocks without considering the following:

1) as mentioned first, an impact study should be done to determine if
unpacking will overflow the available space on the device

2) an unpack routine would need to be written if it doesn't exist.  With my
current knowledge of Reiser and my timeframe (3 weeks) this is not possible
for me to do IMO.

3) the unpack operation would need to treat the previously packed blocks as
sensitive by shredding them after all tails were relocated but before
returning the block to a free list

4) this operation, depending on the outcome of step 1, would be very
expensive in performance

That's all I can think of right now.  Does this sound accurate?

thanks,
brett



             reply	other threads:[~2002-10-25 21:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 21:46 Brett Russ [this message]
2002-10-28  9:55 ` % of filesystem using tails/tail unpacking (shred related) Nikita Danilov
2002-10-28 21:20   ` Valdis.Kletnieks
2002-10-28 22:38     ` Brett Russ
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=HDEFILEPHCPLCAGPLCEMKEMFDFAA.icycle@charter.net \
    --to=icycle@charter.net \
    --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.