From: devzero@web.de
To: Chris Mason <chris.mason@oracle.com>, Lee Trager <lt73@cs.drexel.edu>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Compressed Filesystem
Date: Tue, 16 Dec 2008 19:14:23 +0100 [thread overview]
Message-ID: <545082891@web.de> (raw)
> I'd much rather have just one compression scheme per FS. If people n=
eed
> a specific compression scheme for a specific file, they can just
> compress it in userland.
yes, i also think one compression scheme per FS is absolutely sufficien=
t.
> -----Urspr=FCngliche Nachricht-----
> Von: "Chris Mason" <chris.mason@oracle.com>
> Gesendet: 16.12.08 16:26:28
> An: Lee Trager <lt73@cs.drexel.edu>
> CC: linux-btrfs@vger.kernel.org
> Betreff: Re: Compressed Filesystem
> On Tue, 2008-12-16 at 10:20 -0500, Lee Trager wrote:
> > While I agree that the command you send should be possible it wasn'=
t
> > exactly what I was thinking. Currently I am working on a way for th=
e
> > user to individually set which files/directories they want compress=
ed or
> > not. What I was saying is that assuming you are in a mounted btrfs
> > directory you could do something like
> >=20
> > chattr -R +c zlib dir1 Compress dir1 and all its contents with zlib
> > chattr -R +c bzip dir2 Compress dir2 and all its contents with bzip
> > chattr +c lzo file1 Compress fil1 with lzo
> > chattr -c file2 Uncompress file2
> > chattr +c none dir3 Uncompress dir3 but leave contents as is
> >=20
> > If the user did something like=20
> > mount -o compress,cscheme=3Dzlib /dev/xyz /mntpoint
> > and then
> > chattr +c /mntpoint/dir
> > /mntpoint/dir would default to zlib as would anything else written =
to
> > the disk.
> >=20
>=20
> This is one of those places where more options isn't always better.
> Every option adds complexity to the filesystem and the testing matrix=
=2E =20
>=20
> I'd much rather have just one compression scheme per FS. If people n=
eed
> a specific compression scheme for a specific file, they can just
> compress it in userland.
>=20
> -chris
>=20
>=20
>=20
_______________________________________________________________________
Sensationsangebot verl=E4ngert: WEB.DE FreeDSL - Telefonanschluss + DSL
f=FCr nur 16,37 Euro/mtl.!* http://dsl.web.de/?ac=3DOM.AD.AD008K15039B7=
069a
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2008-12-16 18:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 18:14 devzero [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-15 23:19 Compressed Filesystem devzero
2008-12-16 15:20 ` Lee Trager
2008-12-16 15:26 ` Chris Mason
2008-12-16 16:25 ` Lee Trager
2008-12-16 19:45 ` Roland
2008-12-18 15:55 ` Chris Mason
2008-12-15 22:14 devzero
2008-12-15 23:07 ` Lee Trager
2008-10-27 14:54 Lee Trager
2008-10-28 15:47 ` Chris Mason
2008-10-28 16:33 ` Lee Trager
2008-10-28 17:38 ` Chris Mason
2008-10-28 17:40 ` Zach Brown
2008-10-28 17:46 ` Chris Mason
[not found] ` <53696.2001:470:e828:1::2:2.1225304096.squirrel@avalon.arbitraryconstant.com>
2008-10-29 20:08 ` Chris Mason
2008-11-04 0:08 ` Chris Samuel
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=545082891@web.de \
--to=devzero@web.de \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lt73@cs.drexel.edu \
/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.