From: Hans Reiser <reiser@namesys.com>
To: reiserfs-list@namesys.com
Cc: sean@gutenpress.org, Edward Shishkin <edward@namesys.com>
Subject: Re: Can compression at filesystem level improve overall
Date: Mon, 22 Mar 2004 12:14:02 +0300 [thread overview]
Message-ID: <405EAE5A.8020600@namesys.com> (raw)
In-Reply-To: <200403212317.i2LNHrJo010166@sirius.cs.pdx.edu>
The Amazing Dragon (Elliott Mitchell) wrote:
>>From: Sean Johnson <sean@gutenpress.org>
>>On Fri, 2004-03-19 at 11:53, Nikita Danilov wrote:
>>
>>
>>>That's common misconception. :)
>>>
>>>The goal of compression is to conserve disk bandwidth rather than space.
>>>
>>>By compressing it is possible to transfer data (== uncompressed data
>>>user works with), at a rate higher than raw device bandwidth.
>>>
>>>
>>I am far from any kind of authority on filesystems, but doesn't compression
>>make data corruption a significantly nastier bugaboo?
>>
>>
>
>Potentially. Depending upon the encoding losing one block of encoded data
>maps to losing many blocks of decoded data. Also losing the first block
>of data might make it impossible to recover later blocks.
>
>
I think it will just make you lose the compression atom, but Edward can
say more when he gets back from vacation.
>But these aren't issues since you do error correction near the physical
>layer, and backups just you make sure. You do, don't you?
>
>
>
>
--
Hans
next prev parent reply other threads:[~2004-03-22 9:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 14:25 Can compression at filesystem level improve overall performance? Erik Terpstra
2004-03-19 16:29 ` Redeeman
2004-03-19 16:53 ` Nikita Danilov
2004-03-21 14:29 ` Sean Johnson
2004-03-21 23:17 ` Can compression at filesystem level improve overall The Amazing Dragon
2004-03-21 23:23 ` Sean Johnson
2004-03-22 9:14 ` Hans Reiser [this message]
2004-03-22 8:01 ` Can compression at filesystem level improve overall performance? Kris Van Bruwaene
2004-03-22 18:00 ` Scott Young
2004-03-22 20:04 ` Hans Reiser
2004-03-23 3:03 ` Scott Young
2004-03-23 10:59 ` Hans Reiser
2004-03-24 16:19 ` Scott Young
2004-03-29 5:25 ` Tom Vier
2004-03-29 5:16 ` Tom Vier
2004-03-30 3:34 ` Scott Young
2004-03-30 4:53 ` Tom Vier
2004-03-31 4:51 ` Scott Young
2004-04-08 21:46 ` Tom Vier
2004-04-08 11:47 ` Stewart Smith
2004-03-19 18:59 ` Hans Reiser
2004-03-23 0:17 ` Miguel
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=405EAE5A.8020600@namesys.com \
--to=reiser@namesys.com \
--cc=edward@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=sean@gutenpress.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 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.