Am Freitag, 12. Mai 2006 23:21 schrieb ext Richard Fish:
What I would really like to see is something like reiser4's plugin
scheme brought up to the VFS layer in the kernel, so that any
filesystem could gain transparent compression.
Hmm, wouldn't that be a device mapper task, just like
On 5/14/06, Dirk Heinrichs [EMAIL PROTECTED] wrote:
What I would really like to see is something like reiser4's plugin
scheme brought up to the VFS layer in the kernel, so that any
filesystem could gain transparent compression.
Hmm, wouldn't that be a device mapper task, just like dm-crypt?
On Thursday 11 May 2006 19:51, W.Kenworthy wrote:
What can I use for a compressed file system? I am looking at setting up
a loopback mounted filesystem that I want to use to store backups into.
Compression is needed as space will become a limitation in the future (I
want to do a whole system
since you are not looking at writing to this fs,
then you can use cloop or squashfs
for example, gentoo uses squashfs for its live cd/dvd
squashfs is considered better, but both are in use on live cd/dvd,
cloop was (At least partially) written by the knoppix dude.
typically you get 2.5:1
This is what I currently use: But I dont have room for two archives, and
this method doesnt keep versions. Trying to keep incrementals using
this has proven to be a disaster.
BillK
On Thu, 2006-05-11 at 23:25 -0700, Richard Fish wrote:
On 5/11/06, W.Kenworthy [EMAIL PROTECTED] wrote:
What
I already use reiserfs with notail, but potentially 60G wont go into 40G
of space without compression, and then there is trying to keep
versions ... Its notail is also irrelevant if you backup into a single
file. Same for LVM snapshots (though in this case its a non-LVM laptop
that I want
On 5/12/06, William Kenworthy [EMAIL PROTECTED] wrote:
This is what I currently use: But I dont have room for two archives, and
this method doesnt keep versions. Trying to keep incrementals using
this has proven to be a disaster.
Again, checkout dar. It is specifically designed for doing
William Kenworthy wrote, regarding Squashfs:
and you need at least the
uncompressed space to create the image ... not useful here.
Wrong, you need sufficient disk space to create the compressed filesystem,
that is all.
Phillip Lougher
--
View this message in context:
ted leslie wrote:
big negative (unless fixed in recent releases) is you need enough ram/VM
to hold the entire
fs (to be compressed) in memory. So if you have 512MB ram and a 1GB VM
allocation,
the biggest fs you can archive using cloop/squashfs would be 2.5GB
(approx), that compresses down
William Kenworthy wrote
This is what I currently use: But I dont have room for two archives, and
this method doesnt keep versions. Trying to keep incrementals using
this has proven to be a disaster.
Even though Squashfs is read-only (and so is tar, cpio etc.), you can append
to pre-existing
Richard Fish write:
From what I can tell, there are no really good compressing filesystems
available currently.
I would disagree, Squashfs is an advanced read-only compressing filesystem,
which uses numerous techniques to obtaIn high compression ratios while also
being fast. Some of the
On 5/12/06, plougher [EMAIL PROTECTED] wrote:
Richard Fish write:
From what I can tell, there are no really good compressing filesystems
available currently.
I would disagree, Squashfs is an advanced read-only compressing filesystem,
I should have said read-write filesystem.
What I would
What can I use for a compressed file system? I am looking at setting up
a loopback mounted filesystem that I want to use to store backups into.
Compression is needed as space will become a limitation in the future (I
want to do a whole system backup that so far is 2:1 compressed via
tar.bzip2. I
13 matches
Mail list logo
