From: Andreas Dilger <adilger@turbolabs.com>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: reiser@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: writing a plugin for reiserfs compression
Date: Thu, 1 Nov 2001 13:07:21 -0700 [thread overview]
Message-ID: <20011101130721.D16554@lynx.no> (raw)
In-Reply-To: <Pine.LNX.4.30.0111011754580.2106-100000@mustard.heime.net>
In-Reply-To: <Pine.LNX.4.30.0111011754580.2106-100000@mustard.heime.net>; from roy@karlsbakk.net on Thu, Nov 01, 2001 at 06:14:11PM +0100
On Nov 01, 2001 18:14 +0100, Roy Sigurd Karlsbakk wrote:
> Novell NetWare has a feature I really like. It's a file compression
> feature they've been having since version 4.0 (or 4.10) of the OS.
Yes, there is a patch for ext2 that does this as well.
> New attributes must be added somehow. 'ls' and 'find' and perhaps other
> files must be modified to take advantage of this. The compression job can
> be a simple script with something like
>
> find . -type f ! --compressed ! --dont-compress / -exec fcomp {} \;
>
> (and check can't compress and force compression).
There already exists a patch for reiserfs which uses the same interface
to file attributes that ext2 and ext3 use.
Also, ext2 already has a "compressed", "do not compress", and "dirty"
attributes. They are currently not all user modifyable for ext2
filesystems via chattr/lsattr, but that doesn't mean they cannot be
on reiserfs.
> There must be a way to access the compressed files directly to make
> backups more efficient - backing up already compressed files's a good
> thing.
Yes, there is also such an attribute for "raw" access I think.
Making the user-space interface and tools as compatible as possible is
a good thing, IMHO, just like "ls", "cp", etc all work regardless of
the underlying filesystem.
As a note to whoever at namesys created the reiserfs patch to add the
"notail" flag (overloading the "nodump" flag). I would much rather
that a new "notail" flag be allocated for this. I will contact Ted
Ted Ts'o to get a flag assigned. This will avoid any problems in the
future, and may also be useful at some time for ext2.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-01 20:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-01 17:14 writing a plugin for reiserfs compression Roy Sigurd Karlsbakk
2001-11-01 20:07 ` Andreas Dilger [this message]
2001-11-01 23:01 ` Hans Reiser
2001-11-01 23:09 ` Hans Reiser
2001-11-02 9:29 ` Nikita Danilov
2001-11-01 22:54 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2001-11-01 20:17 Roy Sigurd Karlsbakk
2001-11-01 21:14 ` Andreas Dilger
2001-11-01 21:27 ` Roy Sigurd Karlsbakk
2001-11-01 21:37 ` Padraig Brady
2001-11-01 21:43 ` Roy Sigurd Karlsbakk
2001-11-02 9:24 ` Robert Varga
2001-11-01 23:16 ` Hans Reiser
2001-11-09 23:27 ` Andreas Dilger
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=20011101130721.D16554@lynx.no \
--to=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=roy@karlsbakk.net \
/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